Smart Chat FAQs
What problem does Smart Chat solve?
#Smart Chat stops valuable chats from becoming orphaned browser tabs by keeping threads attached to the notes they serve.
Do I need an API key?
#Not for Core chat codeblocks. They use provider web UIs. Smart Chat API Extension is the Pro workspace for local and cloud API models.
Core codeblocks vs Smart Chat Pro?
#Core codeblocks embed provider web UIs in notes and save thread URLs plus active/done state. Pro adds a dedicated Obsidian chat workspace with model routing, history search, context review, and per-thread controls.
The Pro selector keeps provider creation, saved threads, and active or done groups in one note-attached menu.
Which providers do codeblocks support?
#Codeblocks support ChatGPT, Claude, Gemini, Grok, Perplexity, DeepSeek, AI Studio, Open WebUI, Kimi, and related aliases. See Smart Chat codeblocks.
Does Smart Chat work on mobile?
#On mobile, codeblocks remain useful as thread bookmark lists, but embedded web UIs rely on desktop webview support and do not render the same way. See Smart Chat codeblocks.
How do I save or bookmark a thread?
#Add a Smart Chat codeblock to the owning note, start or open a provider thread, and Smart Chat saves the thread URL into Markdown once the provider URL becomes a real thread link.
Saved threads remain selectable from the note-attached thread menu.
What do Active and Done mean?
#Active means still relevant or waiting on review. Done means you reviewed the thread and closed the loop for now. These are user-owned states. See Chat Inbox.
Done threads remain available while moving out of the active queue.
Does Done mean the AI finished correctly?
#No. Done is a user-owned tracking state, not a claim about model correctness. Promote output into trusted notes only after review. See Smart Loop.
Is Chat Inbox the same as Thread Manager?
#No. Chat Inbox reads note-attached chat-active:: and chat-done:: fields. Thread Manager manages Smart Chat API Extension thread records directly.
Does the Dataview Chat Inbox work without Pro?
#Yes. The Dataview dashboard works with note-attached Smart Chat codeblock fields. Smart Chat API Extension thread management is a separate Pro workflow.
Should I delete done thread links?
#Not automatically. Done thread links can be useful history. Delete them only after reviewing the note and deciding the reference no longer helps.
Can I use local or API models?
#Yes, with Smart Chat Pro. API Extension routes to local and cloud API models through Smart Environment and lets you review context before sending.
Chat settings expose extension, Lookup, and model controls together; this captured configuration still shows a missing model state.
How do I configure an API key?
#Open Chat settings, choose the provider, paste your API key, save, then select the model from the Smart Chat header. See API Extension.
How do I keep a thread from drifting?
#Review attached context before sending, keep stable constraints in custom instructions, and exclude irrelevant message pairs from future context when early turns were exploratory or wrong.
The note-thread insert menu offers Clipboard, Current selection, Current note, or another Note as deliberate source choices.
What if provider sign-in is difficult?
#Use Obsidian Web Viewer to complete sign-in, then refresh the embedded codeblock. If verification loops continue, clear Web Viewer browser data. See Smart Chat codeblocks.