Smart Context FAQs

Smart Context helps you build grounded AI context packages from your actual Obsidian notes, then reuse them across ChatGPT, Claude, Gemini, Smart Chat, or other AI tools.

Yes. Smart Context is clipboard-based, so you can paste exported context into ChatGPT, Claude, Gemini, Smart Chat, or another AI tool without provider lock-in.

Yes. Smart Context runs inside Obsidian and exports to your clipboard. Nothing is uploaded unless you paste copied context into another tool or send it through an enabled provider workflow. See the Privacy Policy.

Core covers fast selection, link depth, named contexts, and template-driven exports. Context Pro adds media-aware copy, external files and repos, heading filters, embedded Bases workflows, and deeper AI context workflows.

Follow Getting Started and run one copy flow: current note, folder snapshot, or reusable context pack.

Use the current note when one note anchors the task, a folder when the project already lives together, and Builder when you need a curated reusable pack.

Depth 0 copies the starting note, Depth 1 adds directly linked notes, Depth 2 adds links of links, and deeper levels expand further. Clipboard shows size estimates.

Start at Depth 0, expand only when needed, watch size estimates, and replace large notes with smaller blocks or selections in Builder.

Yes. Right-click folders, multi-select notes or folders for quick export, or open the selection directly in Builder. See file nav actions.

Yes. Builder lets you create, name, reopen, and reuse trusted context sets across chats and projects.

Type a name in Builder to save it. Reopen or delete saved contexts from the named contexts dashboard row menu. See Named contexts.

No. A named context is a reusable saved set you can open, adjust, and copy without losing your working context. See Builder.

Yes. Send results from the Connections view to Smart Context, remove noise, and copy the curated pack.

Use Clipboard for fast exports, Builder for reusable packs, and Codeblock when a note should carry its own context manifest, especially for repos or external files.

A Smart Context codeblock keeps a visible context manifest inside the note that needs it. Pro can include external files and folders.

Use a named context when the bundle should be reused across many notes. Use a codeblock when the context should stay attached to one specific note and remain visible. See Named contexts.

Yes. Smart Context settings let you customize context templates, item templates, wrappers, file paths, and file tree output.

Yes. Builder supports block selection so you can export only relevant sections. See Builder.

Yes, in Pro. Heading filters can include or exclude specific headings without changing the source note. Configure this in settings.

Yes, with Pro. Copy with media handles images and PDFs, and the Codeblock workflow lets you include external repos or files.

Yes. Smart Context can start from a .canvas file, resolve canvas node links into note references, and apply link-depth rules. See Canvas context.

Yes, in Pro. Embedded Bases can render into copied context, and links in Bases can be treated like normal links during copy flows. See Bases context.

Make the anchor note explicit, include constraints, reduce noise, and tell the model to use only the provided context. Curate the pack in Builder.