Smart Context FAQs

Smart Context helps you copy the Obsidian notes, links, and source material AI needs for the work you are asking it to do.

It is useful when AI answers are weak because the right context is missing, too broad, stale, or hard to check.

Start with the note that already owns the assignment.

1. Open the note with the question, draft, decision, meeting, or project brief.
2. Copy the current note as context.
3. Choose Depth 0 first.
4. Paste into ChatGPT, Claude, Gemini, Smart Chat, or another AI tool.
5. Ask the AI to use only the provided context.
6. Use Depth 1 only when directly linked notes contain details the AI needs.

See Copy current note as context and Getting Started.

There are two proof layers.

Copying proves the plugin did its job. A grounded answer, or a precise missing-context request, proves the workflow is working.

Depth 0 copies just the starting note.

That keeps the first copy small enough to check after paste. It also teaches the most important Smart Context habit:

Copy only the context the assignment needs.

After that first copy works, expand only when the answer shows a real gap or when you already know linked notes are needed.

Depth 1 copies the starting note plus notes it directly links to.

Use Depth 1 when the starting note links to useful support, such as:

• source notes
• examples
• definitions
• decisions
• requirements
• meeting history

Do not use Depth 1 just because the answer was weak. First check whether the starting note has the actual question, outcome, constraints, and useful links.

Depth controls how many link steps Smart Context includes in copy flows that support linked context.

Tighten the starting note and scope before copying more.

Try this:

1. Add the actual request.
2. Add what done should mean.
3. Add the most important constraints.
4. Remove repeated, stale, or irrelevant context.
5. Add or fix links to supporting notes only when they matter.
6. Ask: Use only this context. If anything is missing, list exactly what context is missing.
7. Re-copy at Depth 1 only when directly linked support is needed.

Use Builder when the copied set needs pruning.

First, make the instruction and the starting note more explicit.

Use this recovery prompt:

Use only the provided context.
If the answer cannot be grounded in this context, say what is missing instead of guessing.
List the exact missing note, section, source, or decision.

Then check the starting note:

• Does it state the task or question?
• Does it say what done should mean?
• Does it include the constraints that matter?
• Do the links actually point to supporting notes?
• Is there stale, repeated, or irrelevant text making the request harder to follow?

If those are fixed and the answer still needs support, then increase depth or use Builder.

Yes. Smart Context is clipboard-based, so you can paste copied context into ChatGPT, Claude, Gemini, Smart Chat, or another AI tool.

That portability is the point: copy the right context into the AI workflow you already use.

Smart Context prepares clipboard exports inside Obsidian.

Copied content can leave Obsidian when you paste or send it into another tool, chat provider, or enabled provider workflow. Review the pasted context before sending when your target tool allows.

See the Privacy Policy.

Copying context does not rewrite your notes.

Settings and templates change how copied text is formatted. Builder and named contexts save context selections. Codeblocks write a visible context list only when you choose to use that workflow.

Use the copy method that gives you the right amount of review.

• Current-note copy lets you choose depth before export.
• Builder shows selected sources and size cues before copy.
• File and folder actions are faster direct-copy flows when the scope is already obvious.
• Templates can include source paths, modified times, depth, and a file tree in the pasted output.

After pasting into an AI tool, inspect the copied context before sending when the target tool allows.

Use the smallest method that matches the task.

No. Selected-note, selected-folder, and folder-copy actions are designed for fast export when the scope is already chosen.

Use current-note copy when you need link-depth control.

See file nav actions and Clipboard.

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.

Use this rule:

If you rebuild the same set twice, save it as a named context.

Type a name in Builder to save the current selection.

Open the named contexts dashboard to reopen, copy, edit, or delete saved contexts. Slash names can group related contexts, such as Client/Project/Working Set.

See Named contexts.

No. A named context is a saved set you can reopen, adjust, and copy.

It does not need to replace the one-off set you are building right now.

Use a named context when the same set should be reused across many notes.

Use a Smart Context codeblock when the context should stay attached to one specific note and remain visible in the note body.

Simple rule:

Named context = reuse across many notes. Codeblock = visible context list attached to one note.

A Smart Context codeblock keeps a visible context list inside the note that needs it.

Use it when the note body contains the instructions, brief, or prompt, and the codeblock lists the notes or named contexts that should travel with those instructions.

Context Pro can also include external files and folders in supported desktop workflows.

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

This is the natural handoff:

Discovery finds candidates. Context packages the sources the assignment needs.

Start smaller.

• Use Depth 0 first.
• Use Depth 1 only when supporting notes live one link away.
• Check scope or size cues where shown.
• Replace long notes with relevant blocks in Builder.
• Remove repeated, stale, or irrelevant sources before increasing depth.

Token estimates are directional. Different AI tools count tokens differently.

See Builder and Clipboard.

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

Use blocks when one note contains useful source material mixed with unrelated text.

See Builder.

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

Templates make pasted context easier to inspect because each item can include its source path and metadata.

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

Configure this in settings.

Core covers trusted note-based context:

• current-note copy with link-depth control
• selected-note and folder direct-copy flows
• Builder
• blocks
• named contexts
• codeblocks for notes and named contexts
• template-driven exports

Context Pro adds richer sources and finer control when the assignment needs them.

• Richer sources: media, PDFs, Bases, repos, and external files on supported Pro workflows.
• Finer control: dynamic groups, exclusions, heading filters, and advanced context workflows on supported Pro workflows.

Pro is not required for the first win.

Yes, with Pro on supported workflows.

• Copy with media handles images and PDFs where supported.
• Codeblock can include external repos, folders, or files where supported.
• Bases context can turn a filtered Base into copied context where supported.

Use Pro when the task needs richer sources or finer control. Pro is not required for the first win.

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 on supported workflows.

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

See Bases context.

Core Smart Context is mobile friendly for note-based workflows. Context Pro includes desktop-oriented features, such as external files and folders, that may not be compatible with mobile.