FAQ
Is Engram a vector database?
No. Default Engram search is deterministic lexical search. engram search --semantic adds deterministic local similarity, not embedding-backed semantic search. Graph vectors are local hashed word vectors, not semantic embeddings. Optional local sqlite-vec is an acceleration layer, not the source of truth.
Does Engram write memory automatically?
No. Agents propose candidates; humans approve. Direct terminal CLI uses A/B/C. AI-agent chat uses yes/audit/cancel. Only explicit force requests (ss -f) save every candidate, and agents must not add --force unless the human requested it.
Where does memory live?
- Workspace memory:
<project>/.agents/.engram/ - Global memory: wherever you configure it (default empty until configured)
Workspace memory wins. Global memory is fallback for reusable preferences and team context.
Which agents are supported?
Codex, Claude, Gemini (and Antigravity Gemini-compatible surfaces), Cursor, Windsurf/Cascade, OpenCode, Copilot, Cline, generic AGENTS.md-compatible hosts, MCP-capable hosts, and slash-command hosts. See Agent Integrations overview.
Is encryption implemented?
Encryption config exists, but encrypted storage is not implemented yet. Document current limitations clearly.
Can I use Engram without Git?
Yes. Git is optional but recommended for audit history, portability, and team review.
How do I archive wrong memory?
engram archive --reason "<why>" <id-or-file>
The file leaves active routing only after approval and remains preserved under archive/. Use archive, not delete, for auditability.
How do I move global memory?
engram update-global-folder <new-path>
engram ugf <new-path>
engram move global folder from <old-path> to <new-path>
Add --move-from-path <old-path> when they also want Engram to move the whole old global root into the new location.