Start with Core. Add Pro when a workflow needs more depth.
Core is the shortest path to one result you can inspect from your own notes.
Pro adds higher-change workflows that need more configuration, richer inputs, model-backed operations, performance work, or approved vault action.
Explore Core plugins
Explore Pro plugins
Current product boundary
| Product | Core first-win path | Pro depth |
|---|---|---|
| Smart Connections | Main ranked Connections list, Footer connections, and Smart Lookup. | Inline Connections, Bases relevance, advanced filters/scoring/ranking, current Graph + List renderer, large-vault workflows, Smart Graph handoff, and Dedupe. |
| Smart Context | Text context from notes, blocks, folders, named contexts, codeblocks, current-note depth, link trees, and basic Base source handling. | Composite media image, ZIP output, external files and repositories, dynamic rules, exclusions, heading controls, and richer Base workflows. |
| Smart Chat | Provider-specific note-attached codeblocks and Markdown URL/Active/Done continuity. | Configured local or cloud API Chat, reviewed context attachment, Chat History, and Chat Manager. |
| Smart Templates | Context + Markdown template + instructions -> Copy prompt. | No current Templates-specific generation lane. Generate, Regenerate, Insert, Create note, and output review belonged to Templates v1 and are retired. |
| Smart Graph | Not a Core product surface. | Semantic scopes, selections, clusters, notes, Canvas output, Context handoff, and graph image export. |
| Connect Pro | Not a Core product surface. | Reviewed supported actions through an explicitly connected desktop vault. |
Why Core stays simple
Core should let a new user:
- install one plugin
- open one real note or query
- get one visible result
- inspect the result before trusting it
A smaller Core is easier to learn, document, and keep stable.
Why Pro goes deeper
Use Pro after a specific workflow earns the additional complexity.
Good reasons include:
- related material should appear at the exact block you are editing
- a large or noisy vault needs stronger filtering, ranking, or performance controls
- the assignment needs images, PDF pages, external files, or repository context
- a configured local or cloud model should answer inside Obsidian
- duplicate candidates need a persistent review surface
- a semantic landscape is more useful than a ranked list
- ChatGPT should perform one reviewed action in a connected vault
Pro access does not automatically upload notes. A cloud provider receives only the source text, prompt, or context required by the operation you explicitly run.
Smart Environment ties the suite together
Smart Environment centralizes shared sources, models, exclusions, indexing, events, status, and diagnostics.
A plugin marked Active is loaded. A model marked Current is selected. Neither state proves the first result is correct. Complete one workflow and verify its visible output before expanding scope.
How to evaluate Pro
- Start from a Core workflow that already helps.
- Name the exact limitation.
- Enable one Pro capability that addresses it.
- Run the same real task.
- Keep Pro enabled only when the result is more useful, reviewable, or reliable.
For today's capability boundary, use the current product documentation. Use versioned release notes for historical movement between editions instead of inferring that the boundary has never changed.