Getting started with Pro plugins
Choose one Pro workflow that solves a real problem. The goal is not to activate every plugin; it is to complete and review one result.
The first workflow below uses Context Pro because it produces a visible result without requiring a cloud model or provider key.
Before you start
- Open Obsidian Desktop in the vault where the result belongs.
- Open Browse Smart Plugins.
- Sign in when the Store asks.
- Choose one small source set whose contents you can recognize.
Use this lifecycle throughout Pro:
Installed -> Enabled -> Active -> Configured or Ready -> Successful result
An Active row means the plugin loaded. Continue until the plugin itself produces the expected result.
First win: build and verify one Context Pro package
1. Activate Context Pro
In Browse Smart Plugins, find Context Pro and complete the action shown on its row. Enable or reload when prompted. Continue when the row is Active.
2. Open Context Builder
Run:
Smart Context Pro: Open new context in builder
Add one small folder, tag, named context, or other source whose members you can identify before copying.
3. Review the boundary
Open Rules and confirm what the package includes. Review any existing exclusion or heading rule rather than changing a shared rule only for this test.
A useful first package has a clear purpose and a source set small enough to inspect.
4. Copy and verify the result
Choose Copy context, paste into a clean note, and compare the output with the package you reviewed.
The first win is complete when:
- the expected sources appear
- unrelated sources do not appear
- an existing exclusion behaves as expected
- the pasted output is useful for a real next action
Continue with the Context Rules documentation when you need dynamic include and exclude behavior.
Use the same completion test for any Pro plugin
| Check | Complete when |
|---|---|
| Store | The intended plugin is Active and no enable or reload action remains. |
| Setup | Its required model, provider, source index, permission, or connection is ready. |
| Result | The product produces one visible output that matches the task and has been reviewed. |
Do not evaluate Pro from the Store row alone.
Choose another first result
| Workflow | Start | First complete result | Guide |
|---|---|---|---|
| Connections Pro | Open a meaningful note, then run Smart Connections Pro: Open: Connections view. |
One ranked source is inspected and opened or used. | Connections |
| Context Pro | Open a new context in Builder. | A reviewed package is copied and verified after paste. | Context |
| Chat Pro API | Confirm one working model, then open Chat. | One useful response is generated from the intended context. | Chat |
| Smart Graph | Open a current-note Neighborhood. | One meaningful relationship leads to a real note action. | Graph |
| Smart Dedupe | Open the Duplicate Detector from a note with known overlap. | One candidate pair is reviewed without automatic deletion. | Dedupe |
| Connect Pro | Connect the desktop vault and use the Official GPT. | One clearly named test note appears in Obsidian. | Connect Pro |
When Smart Environment matters
Connections, Lookup, Graph, Dedupe semantic matching, and other indexed-source workflows depend on Smart Environment readiness. Check Smart Environment when known sources are missing or stale.
A provider-backed Chat or Templates workflow also needs one working configured model. Connect Pro instead needs Obsidian Desktop, Obsidian CLI, and an active Connect Pro session.
You are done when
You have:
- activated one Pro plugin
- completed only its necessary setup
- produced one visible result
- reviewed that result in its destination
- decided whether the workflow removes enough friction to keep using it
Only then broaden the scope or enable another plugin.