Smart Context Builder
Smart Context Builder lets you build, save, and reuse AI-ready "context packs" from your Obsidian vault.
If you reuse the same context across sessions (projects, clients, papers, writing pipelines), this removes the worst part of AI workflows:
hunting, copying, pasting, trimming, and re-explaining.

Who this helps
You will feel this immediately if you have ever thought:
- "I keep re-explaining the same project every time I open a new chat."
- "My vault is big, and AI keeps missing the important constraints."
- "I want help drafting, but the output drifts away from my intent."
- "I need meeting continuity: prep and follow-up without losing threads."
- "This note is huge. I only need one section, and I need accuracy."
- "I want to stay inside Obsidian while I assemble context."
If you use the Builder more than once a day, assign a hotkey:
Obsidian Settings -> Hotkeys -> search "Smart Context: Open Selector for New Context".
Two-minute quickstart
Goal: save your first named context that solves a real problem.
- Run:
- Smart Context: Open Selector for New Context
- Add one anchor note (project hub, outline, agenda, or question).
- Add 2-5 supporting items (constraints, references, or examples).
- Enter a name (so you can reuse it).
- Click Copy to clipboard.
- Paste into your AI tool and use one of the "first prompts" below.
If you do only one thing: save a bundle named after a job you repeat.
Pick a problem and save a bundle
Named contexts work best when they are named after the problem they solve, not the folder they came from.
Each recipe below includes:
- What to include (by role)
- Notes vs blocks guidance
- Suggested bundle name
- A first prompt that reliably works
Problem 1: "I keep re-explaining this project every session"
Save this bundle: Project Working Set
Include:
- Anchor: project brief or hub/MOC
- Constraints: requirements, decisions, assumptions, non-goals
- Ground truth: spec, key docs, reference notes
- Examples: prior draft or artifact that you want to continue
- Recency: last status update (blocks: summary + decisions + next actions)
Notes vs blocks:
- Use blocks for meeting notes and status logs.
- Use whole notes for short briefs and specs.
Suggested name:
Project - <Name> - Working Set
First prompt:
- "Using only this context, summarize current state, risks, and the top 5 next actions. Quote the note titles you used for each point."
Problem 2: "AI misses constraints and produces the wrong thing"
Save this bundle: Constraints Pack
Include:
- Anchor: the task you are doing now (question, draft section, decision statement)
- Constraints: requirements, boundaries, decision log, "do not do" list
- Ground truth: the note that defines reality (spec, contract, rubric)
- Examples: one correct prior output or checklist
Notes vs blocks:
- Keep it small. If it is not a constraint, it probably does not belong.
Suggested name:
Constraints - <Project or Topic>
First prompt:
- "Extract all constraints as bullets. Then propose a plan that satisfies every constraint. If anything is ambiguous, ask only the minimum questions needed."
Problem 3: "I want help drafting but it does not sound like me"
Save this bundle: Voice + Draft Pack
Include:
- Anchor: outline + current draft
- Constraints: audience, tone rules, structure rules
- Ground truth: key claims/facts (reference notes)
- Examples: 1-3 pieces you like (your own writing)
Notes vs blocks:
- One strong example beats five weak rules.
Suggested name:
Writing - Voice + Draft
First prompt:
- "Continue the draft in my voice. Use only the provided references for claims. Keep the structure consistent with the outline."
Problem 4: "This note is long. I only need one section and I need accuracy"
Save this bundle: Precision Q&A
Include:
- Anchor: your exact question
- Ground truth: only the relevant blocks from the long note
- Constraints: any formatting rules (bullets, steps, checklist)
Notes vs blocks:
- Prefer blocks-only. Include the definition, the relevant section, and nothing else.
Suggested name:
Q&A - <Topic> - Precision
First prompt:
- "Answer using only these blocks. For each claim, cite which block it comes from by note title and section."
Problem 5: "I need meeting continuity without losing threads"
Save this bundle: Meeting Continuity
Include:
- Anchor: agenda for this meeting
- Constraints: standing goals, roles, sensitive topics, definitions
- Ground truth: project status snapshot
- Examples: your preferred meeting note template
- Recency: last 1-2 meeting notes (blocks: decisions + actions + open loops)
Suggested name:
Meeting - <Series Name>
First prompt:
- "Create a prep brief: agenda, open loops, decisions needed, and the 5 best questions to ask. Then draft follow-up actions."
Problem 6: "My context is too big to fit. I need to stay under limits"
Save this bundle: Token Budget Triage
Include:
- Anchor: your task
- Constraints: the non-negotiables
- Ground truth: the smallest set of blocks that contain the key facts
- Examples: one correct output shape (optional)
Notes vs blocks:
- Replace your biggest notes with only the 1-3 blocks you actually need.
Suggested name:
Triage - <Project or Topic>
First prompt:
- "If this context is still too large, tell me what to remove first, in order, and why. Optimize for preserving constraints and ground truth."
Open the Builder
Run the command:
- Smart Context: Open Selector for New Context

From the same command list, you may also see quick actions like:
- Copy current to clipboard
- Copy entire folder to clipboard
- Help: Show getting started
- Open Management dashboard (show named contexts) view
Select notes with fuzzy search

The Builder uses a native Obsidian-style modal:
- Start typing to filter results (fuzzy search). There is no separate search box - just type.
- Use arrow keys to move the highlight.
- Press Enter to add the highlighted item to your context.

- Blue: Context name input (used to save/reuse a context).
- Pink: The currently highlighted suggestion (press Enter to add it).
- Green: Keyboard hints (Enter to add, Right Arrow to toggle block view, Esc to close).
Mental model: type, highlight, Enter.
You are building a context set the same way you pick commands in the Obsidian command palette.
Use blocks when you need precision
If you want to include only a section of a long note:
- Press Right Arrow to switch into block selection for the highlighted note.
- Select the blocks/sections you want and press Enter to add them.

Notes vs blocks
Choose whole notes when:
- The note is short and mostly relevant
- You want full-document grounding
Choose blocks when:
- The note is long and only 1-3 sections matter
- You are managing a token budget
- You need accuracy on a specific section
Review and manage the selection
As you add items, the top panel becomes a tree view of your current selection.

Remove single items or clear everything

- Remove any individual item with the x control (highlighted in pink).
- Use Clear to remove all selected items at once.
- Watch the total size details (characters and token estimate) to keep tabs on exported context size.
- Use the per-item size to quickly find the biggest items when you need to shrink the bundle.
If the total is getting too large:
- remove the biggest item, or
- swap that note for only the few blocks you actually need.
Save named contexts for reuse
If you assemble the same bundle often:
- Enter a name in the context name field
- Your selection becomes a saved, reusable context
A naming scheme that stays clean over time:
Project - ...Writing - ...Meeting - ...Decision - ...Constraints - ...Q&A - ...
Once you have saved contexts, use the command:
- Smart Context: Open Management dashboard (show named contexts) view
This gives you a fast way to jump back into a known-good bundle without rebuilding it.
Copy to clipboard
When the set looks right, use Copy to clipboard.
That export is designed to be pasted into:
- an AI chat prompt
- a draft note
- a doc you are working on
The copy confirmation now includes depth stats (items per depth) alongside size estimates, so you can spot over-expansion before pasting.
If you want to change how the export is formatted (wrappers, headers, file tree insertion, per-item templates), do that in Smart Context settings.
The Builder is about selection; templates are about output.
Manage named contexts

Use the Management dashboard to browse saved contexts and reopen them quickly.
A simple pattern:
- Keep a few bundles you use weekly
- Reopen and tweak them as projects evolve
- Copy to clipboard when you need AI-ready grounding
Context item types
You can build context from:
- Sources
- Blocks
- Media (Pro)
- Images
- PDFs
- External sources (Pro)
Use media and external sources when:
- the ground truth lives outside your vault
- you want the model to cite or stay anchored to primary materials
Troubleshooting
"The model ignored my notes"
Try this:
- Make the anchor explicit: include the question or task note in the bundle
- Add a Constraints Pack bundle and copy it first
- In your prompt, say: "Use only the provided context"
"My bundle is too big"
Try this:
- Replace the biggest note with blocks
- Remove recency logs that repeat information
- Keep one anchor, one constraints note, and a few high-signal references
"My saved contexts list is messy"
Try this:
- Rename bundles to jobs (Project, Writing, Meeting, Decision)
- Avoid vague names like "Work" unless it is truly stable
- Keep one "Working Set" per active project
Next steps
- Save one bundle you will reuse this week
- Assign a hotkey for the Builder command
- Build a Constraints Pack for your highest-stakes project
If you want: combine Smart Connections discovery with the Builder to turn "interesting finds" into a reusable context pack.