Memory and preferences

You can give future agents useful context without pasting the same background into every conversation. Ask an agent to remember a durable fact or instruction, then inspect the saved memory yourself from the terminal.

Tell an agent what should persist

Say what should be remembered and where it applies.

| If you want to save | Tell the agent | |---|---| | A fact or procedure | “Remember that our staging database is reset every Friday.” | | An instruction about how to work | “Remember that I want a short recommendation before any production change.” | | Something for every project you use | “Remember this as a user preference.” | | Something only agents in this repository need | “Remember this for this project.” |

A preference tells an agent how to act. Knowledge gives it facts or a procedure to consult. The narrowest useful store is best: a user memory follows you everywhere, while a project memory belongs to one repository. For the explanation of memory tiers and loading, see Memory.

Browse what was saved

List the memory documents available in your current context:

crtr memory list

Read one by its name from that list:

crtr memory read <name>

crtr memory read resolves the current winning document when the same name exists at more than one scope. Add --scope user to read only user memory, or --dir <project-directory> to inspect one exact project store.

Edit a memory document

Memory revisions are intentional and recorded. To replace a document's body, pipe the complete replacement text to crtr memory edit and give the reason for the revision:

printf '%s\n' 'Production changes need an explicit approval.' | \
  crtr memory edit <name> --rationale "Updated the approval rule."

crtr memory edit replaces the whole body you pipe; it does not append text. Use crtr memory history <name> to read the revision history. If you want to create a document yourself, use crtr memory write; it requires a kind, a routing sentence that tells agents when to read it, and the document body.

Memory is for reusable current truth and durable instructions, not a transcript of one conversation. When a fact changes, update the existing document rather than saving a second version.