Smart Environment
Smart Environment is the shared local-first runtime that coordinates sources, models, exclusions, indexing, events, status, and reusable components across Smart Plugins.
Local-first describes the default architecture where supported. It does not mean every configured operation stays on-device.
More columns are available. Scroll sideways or use the arrow buttons.
| Operation | Where it runs | What can leave the device |
|---|---|---|
| Local embedding or local model operation | On the device | Nothing is sent to a remote model for that operation. |
| Cloud embedding or ranking | Through the configured remote API | Eligible source text required for that operation. |
| Cloud chat | Through the configured remote API | The prompt and context sent with the request. |
| Clipboard workflow | In Obsidian until paste | The copied package leaves when it is pasted or sent into another application. |
| Connect Pro action | Through the supported connected-vault path | The requested command and the connected-vault interaction required to perform it. |
- Unified runtime. Smart Plugins reuse shared sources, models, exclusions, events, and status instead of rebuilding the same setup in each plugin.
- Modular plugins. Each Smart Plugin focuses on one capability while reusing shared Environment components.
- Troubleshooting. Use status, events, and diagnostics to investigate loading problems and failed operations.
- Explicit boundaries. Review the selected provider, source set, and request scope before sending sensitive material.
New here? Start with Smart Milestones to get started.
Why Smart Environment matters
- New plugins can reuse one source and model foundation instead of creating another silo.
- Core local retrieval can work without uploading the entire vault for every query.
- Provider-backed workflows can make the source and request boundary visible before use.
- Shared status and diagnostics help you troubleshoot indexing and model problems.