Official Smart Plugins site Smart Plugins are independent third-party plugins for Obsidian. Smart Connections is the flagship plugin.
Keep AI conversations where the work lives. Core provider codeblocks save web-thread links in the notes they serve. The Pro universal codeblock brings supported provider threads into one selector. Smart Chat API Extension adds configured local or cloud models and context you review inside Obsidian.
Core: provider links and active/done state | Pro universal codeblock: shared thread selection | API Extension: configured models and reviewed context
Choose a provider-specific Core codeblock, the Pro universal codeblock, or Smart Chat API Extension for the conversation you need.
Use Core when...
Render a provider web interface, save its recognized thread link in Markdown, and track active or done state. The saved link reopens the provider conversation; it is not a transcript stored in the note.
Use the Pro universal codeblock when...
Use one smart-chat codeblock to select supported provider web threads or Smart Chat API Extension threads. Web threads use provider sign-in; API Extension threads require a working configured model.
Use API Extension when...
Choose a configured local or cloud model, attach or retrieve sources, review them before sending, and manage API Extension threads.
Smart Chat Core keeps provider conversations attached to the notes they serve.
Step 1
Use the project, meeting, research, decision, or draft note where the AI thread belongs.
Step 2
Start or open a provider thread using the web UI you already use, such as ChatGPT, Claude, Gemini, Grok, or Perplexity.
Step 3
After a visible provider response creates a recognized conversation URL, save the thread link and reopen it to verify the same conversation. Active/done records track your review state.
You know it worked when the note contains a provider thread link you can reopen later.
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
See the selected/default model before sending.
Proof 2
Add one known source or use Lookup to retrieve candidates for review.
Proof 3
Ask one outcome-focused question in the current API Extension thread.
Proof 4
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.
Pick the guide for the thread state you need to manage.
Add one Core codeblock and save one provider thread link.
Use Core provider blocks or Pro universal selection; saved web links and active/done state stay in Markdown.
Confirm model, review sources, ask one outcome-focused question.
List note-attached `chat-active` and `chat-done` thread links.
Open, rename, search/filter, and clean up API Extension thread records.
Separate Core Markdown link sync from API Extension `.smart-env` storage.
Smart Chat helps preserve or control the conversation. Your note remains the trusted place where reviewed decisions, context, next actions, and deliverables belong.
Watch a thread stay attached to the note it serves.
Core provider codeblocks and Pro universal web threads use provider web interfaces and may require sign-in, without an API model. Smart Chat API Extension threads require a compatible working local model or the credentials required by their cloud provider.
Core stores provider thread links and active/done state in your notes, not the provider transcript. Reopening the link depends on the provider conversation remaining available to your account.
One smart-chat block can select supported provider web-thread references and Smart Chat API Extension thread references. It adds shared provider selection, stable block identity, and managed provider surfaces. Provider web threads remain distinct from API Extension model requests.
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.
Saved provider links sync with Markdown and can open externally on mobile. Embedded provider surfaces and automatic URL capture require the desktop main Markdown pane. API Extension uses Smart Plugin application data, which can remain device-local unless your sync setup includes it. See the mobile/sync FAQ for setup guidance.
Web-provider threads receive what you enter or upload through their interface. API Extension sends your prompt, included prior messages, and the context selected for that response to the chosen model. The active note and whole vault are not attached automatically. Configured cloud embedding or ranking providers can separately receive eligible source text during Smart Environment processing.
No. Chat Inbox reads Core `chat-active` and `chat-done` Markdown fields. Thread Manager manages Smart Chat API Extension thread records.
Save one provider thread link with Core, choose the Pro universal codeblock for shared thread selection, or use Smart Chat API Extension for configured models and reviewed context.
Smart Project lessons
Begin with a four-part introduction, followed by selected lessons from the systems, tools, and workflows behind Smart Plugins.
Subscribe to the Smart Project lessons and selected updates. Unsubscribe anytime. Privacy policy.
