Getting Started with Smart Context
Use Smart Context when you want AI to use your Obsidian notes instead of guessing from a vague prompt.
Start small:
Copy the note that already owns the task.
Add linked notes only when the task needs them.
That first habit matters more than learning every Smart Context feature at once.
- Install Smart Context: https://obsidian.md/plugins?id=smart-context
- Want the overview and upgrade path? See Smart Context.
The goal is not to copy the most context.
The goal is to copy the context the assignment needs.
First win: copy the current note
Use this when one note already contains the task, question, draft, decision, meeting notes, or project brief.
1) Open the note that owns the work
Pick a real note, not a demo note.
Good starting notes usually include at least one of these:
- the question you want answered
- the draft you want improved
- the decision you need help making
- the meeting or project details
- links to notes that contain supporting facts
- constraints, requirements, or what done should mean
2) Copy the current note
Command:
Copy current to clipboard (choose link depth)
Or open the command palette and search for Copy current.
3) Choose Depth 0 first
Depth means "how many link steps should Smart Context include?"
| Choice | Plain meaning | Use when |
|---|---|---|
| Depth 0 | Copy just this note. | The note is enough to start. |
| Depth 1 | Copy this note plus notes it directly links to. | Linked notes contain facts, examples, decisions, or requirements the AI needs. |
Start with Depth 0.
Use Depth 1 only when the linked notes are needed.
4) Paste and ask for a grounded answer
Prompt starter:
Use only this context.
First extract the constraints.
Then answer the request.
If something important is missing, list the exact missing note, section, or source instead of guessing.
5) Check whether it worked
You know it worked when:
- the copied context is small enough to inspect after paste
- the answer uses details from your note
- or the answer clearly names what context is missing
Related deep dive: Copy current note as context
When to use Depth 1
Use Depth 1 when the current note points to important support notes.
Good Depth 1 examples:
- a project hub that links to current status, risks, and decisions
- a draft that links to source notes or voice examples
- a meeting note that links to prior notes and open loops
- a task note that links to specs or requirements
Do not increase depth just because the answer was weak.
First check whether the starting note has:
- the actual request
- the outcome you want
- constraints or requirements
- links to the right supporting notes
Related deep dive: Smart Context Clipboard
What changes when you copy better context
| Before | Smart Context move | What you should see |
|---|---|---|
| AI gives a generic answer. | Copy the note that already contains the task. | The answer uses details from the note. |
| AI misses supporting facts. | Re-copy at Depth 1 when linked notes hold the support. | The answer uses linked notes or names the remaining gap. |
| The copied text is too large to review. | Use Builder to remove noise or select smaller blocks. | The selected sources and size cues are easier to check. |
If the answer is generic
Do this before copying more notes.
- Add the real question or desired outcome to the starting note.
- Add the most important constraints.
- Remove stale, repeated, or irrelevant sources.
- Add a missing source note only when you know it matters.
- Re-copy at the smallest useful depth.
Recovery prompt:
Use only the provided context.
If the answer cannot be grounded in this context, say what is missing instead of guessing.
Choose what to do after the first copy
Once current-note copy makes sense, choose the next method based on the work.
| What is true? | Use this | Why |
|---|---|---|
| One note owns the task. | Current-note copy | Fastest way to start. |
| You already selected the right files or folder. | File navigator actions | Fastest direct export for a chosen scope. |
| The right notes are scattered or noisy. | Builder | Add, remove, and trim sources before copying. |
| You keep rebuilding the same set. | Named context | Save it after repetition appears. |
| The context should stay visible inside one note. | Codeblock | Keep a readable context list attached to that note. |
| The work needs images, PDFs, Bases, repos, external files, dynamic groups, or heading filters. | Pro | Add richer sources or finer control when the assignment needs them. |
Simple rule:
If you rebuild the same set twice, save it as a named context.
If the files or folder are already the right scope
Use file navigator actions when you already know exactly which notes or folder should be copied.
Copy a folder
Use folder copy when the project already lives in one folder.
- Right click a folder -> Copy contents
- Or use the command palette -> Select folder to copy contents
- Multi-select folders -> Copy selected folders from the Files menu where your version supports it
Prompt starter:
Use only this context.
Summarize current status, decisions, open loops, and the top 5 next actions.
Cite the note title for each claim.
File and folder copy actions are fast direct-copy methods. They do not open the same link-depth chooser as current-note copy. If you need link-depth control, start from current-note copy or another flow that supports depth selection.
Related deep dive: Smart Context file nav actions
If the context needs cleanup: use Builder
Use Builder when the first copy is too broad, the notes are scattered, or you want to save the set for reuse.
Builder flow:
- Open the Context Selector.
- Search for notes or use the available suggestions.
- Add the sources that matter.
- Use blocks when a full note is too large.
- Remove anything that does not help the assignment.
- Copy when the selected set is clear.
- Name it only when you expect to reuse it.
Prompt starter:
Extract constraints first.
Then propose a plan that satisfies every constraint.
If anything is missing, list only the minimum missing context.
Related deep dive: Smart Context Builder
Turn useful Connections results into context
Discovery is not the finish line. Useful results often need to become copied context.
Workflow:
- Open the Connections view while working in a note.
- Scan the top matches.
- Send useful results to Smart Context where your version supports it.
- Remove noise in Builder.
- Copy the final set.
Related pages:
Make repeated context easier next time
Templates make copied context easier to inspect
Templates control how copied text is wrapped and labeled.
Use templates to include things like:
- source path
- modified time
- link depth
- file tree
- item wrappers
Deep dive: Smart Context settings
Named contexts save repeated sets
Save a named context when the same set of notes keeps coming back.
Good uses:
- recurring project briefs
- meeting prep packs
- writing voice packs
- client handoff sets
- bug triage bundles
You can reopen saved contexts from the named contexts dashboard. Use slash names to group related contexts, such as Client/Project/Working Set.
Deep dive: Named contexts
Codeblocks keep context attached to one note
Use a smart-context codeblock when the note itself should carry a visible list of context.
Use codeblocks when:
- the note is the brief or prompt
- the context should stay visible in the note body
- repo files, implementation notes, or agent instructions need a durable manifest
Deep dive: Smart Context codeblock
Named context = reuse across many notes.
Codeblock = visible context list attached to one note.
When Pro helps
Core Smart Context covers trusted note-based context.
Use Pro when the assignment needs richer sources or finer control.
| Need | Pro direction |
|---|---|
| Images, screenshots, PDFs, or visual evidence | Copy with media |
| Obsidian Bases as a working set | Bases context |
| Repo files or external folders | External context or codeblock manifest |
| Large changing groups of files | Folders, tags, and exclusions |
| Only certain note sections | Heading filters |
Pro is not required for the first win. It becomes useful when the work needs those sources or controls.
Related pages:
- Copy context with images and PDFs
- Copy filtered Bases rows as linked context
- Smart Context codeblock
Commands and hotkeys
Assign hotkeys for the actions you use daily.
Three command families to remember:
- Copy current to clipboard (choose link depth) -> copy the current note first.
- Smart Context: Open Context Selector -> build or trim a set before copying.
- Smart Context: Open Context Dashboard -> reopen saved named contexts.
Obsidian Settings -> Hotkeys -> search Smart Context.
Pick one daily workflow and make it one keystroke.
Next steps
Start here:
Then branch when the work needs it: