Skip to content
1AIVault1AIVault

1AIVault Documentation

Common Issues

Diagnose missing imports, MCP reads, topic classification, Auto-Inject, and license limits.

Use these checks before changing files manually.

No Conversations Detected

Run Collect -> Rescan. Confirm the source app has written at least one conversation and that the row shows a data path. Some browser sources require the companion extension instead of direct desktop parsing.

Import Stops Early

If the Free entry cap is reached, 1AIVault shows an import-limit dialog. Upgrade or remove unused entries before importing more.

MCP Client Cannot See the Vault

  1. Re-run the installer in Connection -> Install MCP.
  2. Restart the AI client.
  3. Check the client-specific MCP list.
  4. Open Connection -> Diagnostics and confirm the server script and database are ready.
  5. Check Activity and Memory Reads for the attempted query.

AI Reads Return No Results

The client may be connected but searching for content that has not been imported. Open Memory Reads, inspect the empty query, then import or save the missing context.

Classification Is Pending

Open Classify and use Classify Now. The wizard helps you select an MCP-connected AI client, check MCP status, and copy the prompt. You can also use Ollama-based workflows where configured.

Auto-Inject Does Not Appear

Start a fresh AI session after enabling a target. Static instruction files are read at startup, not mid-session. For Claude Code, check whether the SessionStart hook is installed.

License Looks Wrong

Open Settings -> License and use Validate License. If device counts are wrong, deactivate old devices through the Lemon Squeezy customer portal.