Skip to content
On this page

Getting Started with Smart Chat

Use a Smart Chat provider codeblock in the note where the conversation belongs. The block can show ChatGPT, Claude, Gemini, or another supported provider.

This page starts with Core provider codeblocks. They use provider web interfaces and do not require an API model or Smart Environment retrieval.

Choose the right Chat surface

Surface Use it to
Core provider codeblock Open a provider such as ChatGPT, Claude, or Gemini inside a note.
Universal Smart Chat codeblock (Pro) Keep supported provider conversations or Smart Chat API Extension thread references in one smart-chat codeblock.
Smart Chat API Extension Chat with a configured local or cloud model in the Smart Chat workspace, with notes attached when needed.

For Smart Chat API Extension, use Smart Chat API Extension Getting Started.

Before you start

You need:

Core provider codeblocks use provider web interfaces. You do not need an API key, a configured chat model, or an Environment index for this workflow.

Tip

You can still use local models in Core with the Open WebUI codeblock if you already run Open WebUI locally.

Activate Core Smart Chat

Use this sequence:

  1. Open Browse Smart Plugins.
  2. Find Chat.
  3. Follow the visible Install or Enable action.
  4. If Enable appears after installation, choose Enable.
  5. If the row shows a full Reload required... action, complete it.
  6. Continue when the Smart Chat row shows Active.

Current Smart Plugins Store with Chat Core installed and ready to enable

1. Open the note where the chat thread belongs

Start from the note that owns the work.

Good candidates:

The simple rule:

Put the chat thread in the note where future-you would look for it.

2. Insert a provider codeblock

Open the Command Palette in the owning note. Run the provider action that you need. For ChatGPT, run Insert OpenAI ChatGPT codeblock.

Other Core actions include:

The ChatGPT action inserts:

```smart-chatgpt
```

Switch the note to Reading view so the provider surface can render. For fences, providers, and Pro differences, see Supported providers.

3. Open the provider surface

In Reading view, open the provider from the rendered block. If the provider requires an account, sign in.

Chat Core provider selector showing New Codex and New chat, with New chat selected and the thread still Unsaved

New chat and Unsaved identify a loaded provider surface, not a completed or durable thread.

4. Send the first prompt

Enter a small, useful prompt:

Create a five-item review checklist for this task: [describe the task in one sentence].
Keep each item specific and testable.

Replace the bracketed text with the task owned by the note.

Send it with the provider's normal send control.

You know Chat is working when the provider displays a response that fits the request. Use that response for the note's work. Ask a follow-up question for any missing detail.

Response success and thread saving are different

A provider can return a response while the block still shows a new or unsaved chat.

5. Save the thread when a durable URL exists

After the provider creates a recognized conversation URL, Smart Chat can write the reference into the codeblock. Reopen the saved entry. Make sure that it returns to the intended conversation.

Example saved state:

```smart-chatgpt
chat-active:: 1700000100 https://chatgpt.com/c/example-active
```

If the surface still says new chat or no URL appears, the response can still be valid. However, the thread is not yet a durable note bookmark. Continue the provider conversation until it creates a recognized URL. Alternatively, use Copy link only when the current URL identifies the conversation.

Core stores saved URLs and Active or Done state in Markdown. It does not store the full provider transcript by default.

Optional: Mark active or done after review

State Meaning Use it when
chat-active:: The thread is still relevant, waiting, or in progress. You need to return later.
chat-done:: You reviewed the thread and closed the loop for now. The useful output has been handled, promoted, saved, or dismissed.

See Mark done and Mark active.

When to use the universal Smart Chat codeblock

Smart Chat Pro adds the universal smart-chat codeblock. Use this sequence:

  1. Run Insert Smart Chat codeblock.
  2. Switch the note to Reading view.
  3. Choose a provider from New chat.
  4. Send a concrete prompt.
  5. Confirm that the provider returns a settled visible response.

Universal Smart Chat New chat menu with provider choices

Choose the provider for the new thread.

Universal Smart Chat codeblock with a settled ChatGPT response inside the research note that owns the work

The provider responds inside the note. Saving a bookmark requires a recognized conversation URL.

Use it when one codeblock needs a shared provider selector or several saved provider threads. Durable URL capture and Active or Done tracking remain separate checks.

Desktop vs mobile

Platform What to expect Best use
Obsidian Desktop Embedded provider surface, sending, URL capture, and thread controls Full workflow
Obsidian Mobile Saved URLs can remain useful as external bookmarks. The embedded provider workflow is unavailable. Reopen saved conversations
Any text editor Saved provider URLs and Active or Done fields remain readable Markdown Recover known links

On mobile, use saved URLs as bookmarks or external links. Use desktop for the full embedded provider interface. See the platform reference.

Recover the first workflow

Problem Recovery
Provider surface is blank or stalled Use Refresh. If sign-in is required, complete it in Obsidian Web Viewer. Return to the block. Use Refresh again.
The provider rejects the prompt Make sure that sign-in works. Make sure that the account has provider access. Make sure that the provider is available. Retry the same small prompt.
A response appears but the block still says new chat Treat response success as complete, but not durable saving. Wait for a recognized conversation URL before relying on the bookmark.
A saved entry opens the wrong conversation Return to the correct provider thread. Save or select its exact URL.
The embedded provider is unavailable on mobile Open an already saved URL externally or continue on desktop.

Continue with another Chat task

Next need Continue with
Ground a provider request with a small reviewed source set Smart Context Getting Started -> Docs
Find a source by meaning when you know the question, not the note Smart Lookup Getting Started
Apply a specific vault change Connect Pro Getting Started
Review Active and Done links across notes Build a Chat Inbox
Use a configured local or cloud API model inside Obsidian Smart Chat API Extension Getting Started -> Docs
Understand every provider, selector, action, and recovery path Smart Chat codeblock documentation