Smart Environment FAQs

Smart Environment is the shared system Smart Plugins use for source discovery, import, embedding preparation, model configuration, background work, status, events, and diagnostics.

It prepares data for indexed workflows such as Connections, Lookup, Graph, and semantic Dedupe. A provider codeblock or model-backed Chat request may not need indexed Environment sources unless that workflow uses Lookup or other retrieval context.

Smart Environment stores generated local data under .smart-env/ in the vault. Your Markdown notes remain the source material. Smart Environment can rebuild .smart-env/ from eligible content and current settings.

Exclude .smart-env/ from third-party file synchronization such as Syncthing unless the guidance for your specific setup says otherwise. It is generated index state, can create unnecessary writes and conflicts, and can be rebuilt on each device from the vault's source files.

This recommendation is for third-party folder sync. Follow the current instructions for the sync product you actually use.

The status view also provides Pause embedding, Open events feed, Environment stats, and Browse Smart Plugins.

Use the checks required by the workflow:

1. The plugin is active and its provider, model, or plugin-specific settings are complete.
2. When the workflow uses indexed sources, Environment shows Smart Environment ready or Ready.
3. Environment stats shows the required Sources or Blocks as eligible and current.
4. The plugin produces one result you can inspect.

1. Smart Environment ready means loading, import, and embedding work are idle.
2. Open events feed and Environment stats help diagnose retained issues or source coverage.
3. Browse Smart Plugins returns to installation and activation controls.

Ready does not mean every plugin is configured, every result is relevant, or every workflow will be fast.

Open Smart Environment settings. Read Default embedding model. Use the model marked Current rather than relying on a remembered name.

Re-index embeddings and Test model are separate actions. Selecting a model does not make its embeddings current or prove that the model test passed.

A model selection affects future embedding preparation. It does not instantly replace existing vectors.

1. Confirm that the intended model is marked Current.
2. Choose Test model when you need to verify that the selected model can run.
3. Choose Re-index embeddings to prepare embeddings for the selected model.
4. Resume embedding when it is paused.
5. Wait for Smart Environment ready or Ready.
6. Check the required Sources or Blocks collection in Environment stats.
7. Refresh or reopen the product result.

Use Reset data only when Environment source data itself needs a broader rebuild. For a normal model change, use the dedicated Re-index embeddings action.

Use these settings:

• Manage excluded folders for folder exclusions
• Manage excluded files in Pro for individual files
• View all exclusions to review the combined boundary

1. Folder exclusions
2. Pro file-level exclusions
3. Combined exclusions review
4. Block embedding and minimum-length controls

Excluded content is not eligible for Environment indexing or index-backed semantic retrieval. After changing an exclusion, inspect the affected note or review Environment stats before judging ranking again.

Rapid edits or sync activity can queue repeated re-import work. Increase Re-import wait time gradually so changes can settle before automatic re-import begins. This delays preparation. It does not disable indexing.

When the status view shows Queued re-import work, choose Run re-import to start it immediately.

Environment stats separates discovery, eligibility, and current embedding preparation.

1. Total indexed items
2. Work still needed and unexpected vectors
3. Sources eligibility and coverage
4. Blocks eligibility and coverage

Check the collection used by the product workflow. Treat Unexpected as a cleanup signal, not as missing work.

Keep the note active. Choose Inspect active note from the Smart Environment status menu. Check its source eligibility, exclusions, and the Source or Block state required by the workflow before changing retrieval settings.

Open Environment stats. Review eligible items, current embeddings, Sources and Blocks coverage, and exclusions.

If embedding is paused, choose Resume embedding. If re-import work is queued, choose Run re-import. Use Open events feed for retained warnings and errors.

No. Ready is a loaded-and-idle state. Coverage describes preparation. Neither measures relevance, answer correctness, startup time, or performance in another vault.

Test the actual workflow with a representative note, query, or prompt. Compare the same task when evaluating speed or quality.

Reset data or Re-import sources rebuilds Smart Environment source data and starts preparation again. Eligible content may then need new embeddings. It does not delete your Markdown notes.

Use Export data when you need a diagnostic JSON snapshot of sources, blocks, and optional vectors without resetting Environment.

Embed blocks makes eligible sections inside notes available as smaller retrieval units. It can improve precision for long notes, but it also increases the number of items, storage, and compute. It does not guarantee more relevant results.

Cloud providers require their own credentials and connectivity. Review the selected provider before processing sensitive material.

No. Mobile can defer Environment loading to keep startup lighter and make resource-heavy preparation explicit. Use this sequence before you test an indexed workflow:

1. Choose Load Smart Environment.
2. Keep the status view open.
3. Wait for Smart Environment ready or Ready.

Mobile devices have tighter startup, memory, battery, and background-processing constraints. Deferred loading lets you choose when Environment work begins instead of making every vault launch pay that cost.

Use this sequence:

1. Open the Environment status view.
2. Choose Load Smart Environment.
3. Watch the loading, import, and embedding states.
4. Wait until Environment reaches Ready.
5. Run one product-owned result. For example, open Connections for a meaningful note or run a Lookup query.

Manage muted notices in Smart Environment settings. Muting a notice does not remove the retained event. Use Open events feed to inspect it later.