ContextVaultDocs
Documentation/Reference/Troubleshooting
← All guides

Reference

Troubleshooting

Diagnose common capture, import, project selection, and search issues.

Reference · Help

Troubleshoot the common paths

Missing context usually means a source has not been exported/imported, the active folder differs, or the index needs rebuilding.

01The CLI says command not found+

Use npx @aliabdm/contextvault init, or install with npm install -g @aliabdm/contextvault. Check that Node.js is installed and reopen the terminal after a global install.

02No sessions appear in Desktop+

Check Active project. Terminal and Desktop must use the same folder; each project has its own .contextvault directory.

03An extension conversation is missing+

Extension captures are in browser IndexedDB. Export the conversation or ZIP from the popup and import the downloaded file into the intended project.

04Imported content is missing from Search+

Rebuild the index from Vault Tools, or run contextvault index from the project root. Verify filters and query text.

05A session was saved to the wrong project+

The CLI uses the current working directory. Desktop uses the selected Active project.

06Remove Project made my project disappear+

Remove clears only the Desktop recent list. It does not delete the folder or .contextvault data; add the folder again to reopen it.