Memory commands.
Turn decisions, preferences, and project context into durable memory that every connected tool can recall.
Why Empirical memory exists
Chat context disappears when you change tools, projects, or sessions. Empirical gives that context a durable home, then scopes and retrieves it when an agent needs it. Store decisions, constraints, preferences, and concise project facts—not a transcript of every conversation.
- Personal preferences that should follow you
- Workspace-specific decisions and constraints
- Handoffs another agent should be able to recover
Read memory
Query is the normal natural-language entry point. Use get when automation already knows the ID, and list for a filtered or paginated inventory. Add --path to a query when you want to force one retrieval pathway instead of letting Empirical choose.
empirical memory query --match "What are this project's deployment constraints?" --top-k 8 --pretty
empirical memory get --memory-id <id> --pretty
empirical memory list --category project --limit 20 --prettyWrite memory
Record a standalone memory when the information can be understood later without the original conversation. Note appends context to an existing record; update changes its durable fields.
empirical memory record --category decision --summary "Deploy docs from main after the build passes"
empirical memory note --match "Deploy docs from main" --text "FTP upload remains a separate release step"
empirical memory update --match "Deploy docs" --patch-json '{"summary":"Deploy docs from main after build and upload verification"}'Maintain and export
Use delete only when a record is genuinely obsolete, review duplicate candidates before merging, and export before a migration or major cleanup.
empirical memory duplicates --memory-id <id>
empirical memory merge --canonical-id <canonical-id> --duplicate-id <duplicate-id>
empirical memory delete --match "obsolete preference" --confirm
empirical memory export --scope personal --out ./empirical-memories.jsonLast updated: July 31, 2026