Choose Core or Pro by the work
Core completes useful free workflows with your notes. Satisfied free use is a valid outcome, not an unfinished trial.
Evaluate Pro directly when an existing recurring task needs a verified paid contribution. Core does not have to precede that evaluation. Pro can add finer controls, richer inputs, configured API chat, local indexing, or enabled source-access and action tools.
Explore Core plugins
Explore Pro plugins
Current product boundary
| Product | Complete Core workflow | Specific Pro contribution |
|---|---|---|
| Smart Connections | Connections view, Footer connections, related-source actions, and the 2D similarity map / mini graph. | Inline Connections, Bases integration, advanced filters/scoring/ranking, and 2D/3D semantic neighborhoods with note-link overlays. Smart Graph and Smart Dedupe are separate plugins, not paid switches for the Core mini graph. |
| 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. | Universal provider/API codeblock and Smart Chat API Extension with configured models, reviewed context attachment, saved API threads, and per-thread instructions. History searches thread names and recent prompt previews, not every message's full text. |
| 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. | Enabled tools in a running desktop vault through independent Local MCP, Smart CLI, or Remote GPT routes. Dedicated proposals wait for Inbox review; other enabled writes can run directly. |
| Smart Dedupe | Not a Core product surface; ordinary related-note discovery does not require cleanup. | Review exact or semantic duplicate candidates. No automatic merge or deletion. |
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
- a supported AI app needs current project sources or a dedicated proposal reviewed in the desktop vault
The local index does not require a third-party vector database. A configured cloud embedding/ranking provider or connected AI app can receive source content as part of the workflow. Local transport does not establish that the model runs locally; check the selected provider and app's privacy terms.
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
- Name an existing recurring task and how you handle it now. The alternative may be Core, manual work, or another AI tool.
- Identify the exact obstacle and the verified Pro capability that addresses it.
- Complete only that capability's required setup, then run a representative real task.
- Compare useful results and total preparation, review, and repair effort with the current approach.
- Use another genuine occasion to judge recurring value. Keep Pro when its contribution earns its place; a successful Core result does not require an upgrade.
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.