Use Core when...
The thread should stay attached to a note
Save official provider thread links in Markdown, return later from the originating note, and track active or done state.
Smart Chat
Keep AI conversations where the work lives. Start with Core codeblocks to save provider thread links in the notes they serve, then use Smart Chat API Extension when you need model choice, reviewed sources, and API Extension thread control inside Obsidian.
Core: saved provider thread links in Markdown | API Extension: model, sources, thread, and response visible before trust
Choose by the job
Core is complete for provider-thread continuity. Smart Chat API Extension adds model and source control when the conversation needs it.
Use API Extension when...
You need to set up API Models
Choose a configured local or cloud model, attach or retrieve sources, review them before sending, and manage API Extension threads.
Start with Core: save one thread link
Smart Chat Core keeps provider conversations attached to the notes they serve.
-
Step 1
Open the note
Use the project, meeting, research, decision, or draft note where the AI thread belongs.
-
Step 2
Add a provider codeblock
Start or open a provider thread using the web UI you already use, such as ChatGPT, Claude, Gemini, Grok, or Perplexity.
-
Step 3
Save the thread link
The note now contains a thread link or active/done state that can be reopened later.
You know it worked when the note contains a provider thread link you can reopen later.
Advanced configuration: Add Smart Chat API Extension
API Extension is the Smart Chat path for local or cloud models you have set up, source review before sending, custom instructions, and API Extension thread recovery.
-
Proof 1
Confirm model
See the selected/default model before sending.
-
Proof 2
Attach source
Add one known source or use Lookup to retrieve candidates for review.
-
Proof 3
Use thread
Ask one outcome-focused question in the current API Extension thread.
-
Proof 4
Review response
Promote only the parts that match your outcome and sources.
You know it worked when the model, sources, thread, and response are visible before you trust the answer.
Smart Chat guides
Pick the guide for the thread state you need to manage.
Start here
Getting Started
Add one Core codeblock and save one provider thread link.
Core
Smart Chat codeblocks
Save provider thread links and active/done state in Markdown.
API Extension
Model and source control
Confirm model, review sources, ask one outcome-focused question.
Core dashboard
Chat Inbox with Dataview
List note-attached `chat-active` and `chat-done` thread links.
API Extension dashboard
Thread Manager
Open, rename, search/filter, and clean up API Extension thread records.
Mobile and sync
Mobile/sync FAQ
Separate Core Markdown link sync from API Extension `.smart-env` storage.
The thread is not the deliverable
Smart Chat helps preserve or control the conversation. Your note remains the trusted place where reviewed decisions, context, next actions, and deliverables belong.
- Open the note that owns the work.
- Reopen the saved provider thread or API Extension thread.
- Compare the output against the outcome and sources.
- Promote only the useful parts.
- Mark the thread done or keep it active with a clearer next action.
See Smart Chat in action
Watch a thread stay attached to the note it serves.
FAQ
Do I need an API key?
Not for Core chat codeblocks. Core uses provider web UIs and saves provider thread links in Markdown. Smart Chat API Extension uses local or cloud API models you have configured in Smart Environment.
What does Core store?
Core stores provider thread links and active/done state in your notes. It does not store the full provider transcript by default.
What does Smart Chat API Extension add?
It adds the API integration for configured local or cloud models, reviewed sources before sending, custom instructions, include/exclude controls, and API Extension thread history/management.
Does this work on mobile?
Core codeblock links sync as Markdown and can be opened from mobile. The full embedded provider web UI is desktop-first. Smart Chat API Extension stores thread data in `.smart-env`, which is not recommended to sync by default. See the mobile/sync FAQ for setup guidance.
Is Thread Manager the same as a Chat Inbox?
No. Chat Inbox reads Core `chat-active` and `chat-done` Markdown fields. Thread Manager manages Smart Chat API Extension thread records.
Start by saving one provider thread link in the note it serves. Add Smart Chat API Extension only when choosing the model and reviewing sources before sending matters.