Smart Environment

Smart Environment is the shared local layer that powers Smart Plugins. It prepares sources, models, providers, settings, exclusions, indexing, events, and status once so Connections, Lookup, Context, Chat, Templates, Graph, and companion plugins can work from the same environment.

Build the local layer once

Smart Plugins are intentionally modular, but they should not make you repeat the same setup in every plugin. Smart Environment gives the suite one place to manage the foundations that every workflow reuses.

• Shared sources. Notes, blocks, folders, and indexed collections are prepared once for the plugins that need them.
• Shared models and providers. Local and remote model options are managed from the same environment instead of scattered across every feature.
• Shared exclusions and settings. Keep noisy, private, or out-of-scope material out of workflows from one control plane.
• Shared events and status. Indexing, loading, warnings, and milestones stay visible so you can inspect what happened.

Why Smart Environment matters

• Less duplicated setup. Build the local layer once; reuse it across Smart Plugins.
• Clearer trust boundaries. Local workflows and provider-backed workflows are easier to understand when the boundary is visible.
• More consistent behavior. Plugins work from the same prepared environment instead of creating separate silos.
• Better large-vault support. Performance-sensitive semantic workflows can reuse shared local performance tooling where available.
• More inspectable workflows. Events, status, and settings make the system easier to review and tune.

Local-first, with explicit provider choices

Core retrieval workflows can run locally after indexing, and provider-backed workflows are opt-in. Third-party providers only see the content you explicitly send through enabled integrations. For exact legal and service boundaries, use the current privacy and license docs.

Status and visibility

Smart Environment keeps loading, embedding, notices, warnings, and milestones visible. On desktop, status can surface through the status bar and events feed. On mobile, Smart Environment uses a dedicated status view so loading and embedding are inspectable even without a persistent desktop-style status bar.

• Confirm when sources are loading.
• Watch embedding progress and ready state.
• Review events and warnings after the environment finishes preparing.
• Mute noisy notifications while keeping events available for review.

How the pieces fit

• Smart Connections and Lookup use the environment for local embeddings, indexing, result settings, and semantic retrieval.
• Smart Context uses the environment to package notes, blocks, folders, and saved contexts into reviewable bundles.
• Smart Chat uses the environment for provider/model settings and context-aware chat workflows.
• Smart Templates uses the shared workflow layer when structure and context need to become repeatable prompts or generated outputs.
• Smart Graph and Dedupe can use shared semantic data and local performance tooling for calculation-heavy workflows.