Getting Started with Smart Plugins

Use this page when deciding where a workflow belongs.

Smart Plugins work best when you start with one surface, get one visible result, and add the next layer only when a specific need appears.

One command, one result, one sign it worked.

For the step-by-step first-win guide, start here:
Getting Started with Smart Plugins

Before evaluating results

Smart Plugins may need a little preparation before Connections or Lookup can show useful results.

If this is your first run, or if results look empty or stale, check Smart Environment readiness before deciding the workflow failed.

Open Smart Milestones to see whether import and embedding are complete or still preparing.
Review Smart Environment settings if you need to confirm sources, exclusions, embedding models, provider settings, or status.
On mobile, use the Load Smart Environment flow.

You are ready to test when status is visible and one real note can act as the anchor.

The compressed chooser

Use this rule when you are not sure which surface to open:

Current note -> Connections. Question -> Lookup. Exact phrase -> Obsidian search. Landscape -> Smart Graph. Reusable set -> Context. Repeatable form -> Templates. Durable thread -> Chat. Action -> Connect Pro. Duplicate cleanup -> Dedupe.

Use the surface that matches the job in front of you.

Core first

Start here when you want the shortest path to one useful result from your own notes.

User intent	Best surface	You know it worked when...	Start here
I am writing in a note and want related material	Smart Connections	One relevant result appears from the current note and is previewed, opened, or dragged.	Smart Connections
I have a question or idea but not the exact words	Smart Lookup	One useful result appears from a plain-language query and can be verified from preview.	Smart Lookup
I know the exact word, filename, heading, tag, or regex	Obsidian search	The exact match appears.	Obsidian native search
I need reusable context for AI	Smart Context	One reviewable context bundle is copied or saved.	Smart Context
I need structure for repeatable output	Smart Templates	One structured prompt is copied from current work.	Smart Templates
I need a thread that stays with the work	Smart Chat	One thread URL or state is saved in the originating note.	Smart Chat
I need setup, source, model, or indexing status	Smart Environment	Local setup status and sources are visible.	Smart Environment settings

You do not need the whole suite on day one.

Pick one surface, reach one visible result, then add the next layer only when the work asks for it in a specific way.

Fastest Core start

Start with Smart Connections if you are new.

Confirm Smart Environment status is visible or ready enough to test.
Open a real note with enough text to anchor results.
Open the Connections view.
Scan the top results.
Preview one result.
Drag one useful link into your note, or open the note to confirm it.

Your first win:

You recovered one useful note from your own vault without reorganizing first.

If the current note is too small or empty, use a richer note.
If you have a question instead of an anchor note, use Lookup.
If you know the exact phrase, use Obsidian search.

Core paths

Smart Connections

Use when the current note is the anchor.

Best for:

related notes while writing
recovering useful context without folder hunting
linking while writing
sending strong matches to Smart Context

You know it worked when:

A related note appears, and you can preview, open, or drag it into the current note.

Start here:
Smart Connections getting started

Smart Lookup

Use when the question is the anchor.

Best for:

asking your vault a plain-language question
finding notes by meaning
recovering ideas when you do not remember exact wording
sending results into Smart Context

You know it worked when:

You type a natural query and recover one useful note by meaning.

Start here:
Smart Lookup search workflow

Smart Context

Use when selected notes need to become AI-ready context.

Best for:

copying the right notes into an AI tool
building reusable context packs
controlling link depth
reducing missing or bloated context

You know it worked when:

You copy one reviewable context bundle and paste it into your AI tool or Smart Chat.

Start here:
Smart Context Clipboard

Smart Templates

Use when the output needs repeatable structure.

Best for:

starting from the current note or selection
adding context before choosing a template
choosing trusted Markdown templates
copying a structured request

You know it worked when:

You produce one structured prompt from current work.

Start here:
Smart Templates clipboard workflow

Smart Chat

Use when the thread should stay attached to the work.

Best for:

saving provider thread URLs into the note they serve
marking threads active or done
returning to a thread without hunting browser tabs
pairing chat with Smart Context

You know it worked when:

A chat thread is attached to the note where the work lives.

Start here:
Smart Chat getting started

After a specific need appears

Use these paths after Core has produced value or when you already know the specific workflow gap.

Need after Core value	Best path	You know it worked when...	Start here
Lists feel too flat and you need topic shape	Smart Graph	One visible cluster or neighborhood becomes a next action.	Smart Graph
Repeated blocks or repeated context are costing attention	Smart Dedupe	One likely repeated block is reviewed side by side and turned into a decision.	Smart Dedupe
Chat needs to apply an approved vault change	Connect Pro	One low-risk command result or vault change is reviewed.	Connect Pro
Context needs media, PDFs, Bases, external files, or repos	Smart Context Pro	Advanced evidence travels with the assignment.	Copy context with images and PDFs
You want generation and review inside Obsidian	Smart Templates Pro Generate	One generated output is reviewed before insertion.	Generate inside Obsidian
Model routing or API workspace matters	Smart Chat API Extension	The model, attached context, and thread are visible before trusting the next response.	Smart Chat API Extension
Semantic workflows feel heavier as the vault grows	Pro performance path	Performance/index state is visible and enabled where relevant.	Smart Environment settings

Core remains useful.

Pro adds advanced workflows when you need more context, faster retrieval, model routing, generation, cleanup, graph, or approved vault action.

How the suite compounds

A simple Core loop can look like this:

Open one real outcome note.
Use Connections or Lookup to find the most relevant notes.
Use Context to package the smallest useful bundle.
Use Chat or your current AI tool to delegate from the note.
Review the output.
Improve the note so the next pass starts stronger.

That is the Smart Loop in practice:

Make the work clear. Send the note with context. Improve the note from the result.

You can run the pattern manually.
Smart Plugins reduce the friction of doing it repeatedly inside Obsidian.

If the first result is weak

Do the smallest fix that matches the symptom.

Symptom	Recovery
Connections shows nothing useful	Check Smart Environment readiness, use a richer anchor note, or tune sources/settings.
Lookup misses the phrase you typed	Use Obsidian search for exact phrase/title/tag/regex.
Lookup results are too broad	Add context nouns and a desired output to the query.
Context copy is too large	Lower depth, reduce selected notes, or use Builder to remove noise.
Chat answer is generic	Review or add context before blaming the model.
Thread gets lost	Save the thread URL/state in the originating note.
Similar notes look like duplicates	Use Dedupe for review-first cleanup, not Connections ranking.
The list is useful but too flat	Use Graph when the landscape matters more than a list.

Next steps

Pick one surface.
Reach one visible result.
Add the next Smart Plugin only when a specific need appears.

Start with Core:
Start with Core plugins

Explore Pro after a real workflow gap:
Explore Pro plugins

Use the step-by-step first-win guide:
Getting Started with Smart Plugins