Memory you review: proposals, Dream and a side chat that does not interrupt
MendCode’s memory waits for your review by default. Dream proposes memories from session digests, /memory shows all of it in nine tabs, and /btw asks about a running session without stopping it.
Review first
An agent that quietly decides what to remember about you is hard to trust. In MendCode a memory the agent, Dream or Evolution proposes follows its category’s policy, and the default policy is review: the proposal waits in Pending until you approve it.
Policies
| Policy | A proposal is |
|---|---|
| auto | saved at once |
| review | kept in Pending (the default for most categories) |
| never | dropped (the default for volatile, one-off details) |
Two safeguards that hold whatever the policy says
- A proposal in which a secret was redacted always waits for review.
- What you add yourself is always saved.
Nine tabs
/memory (or /mem) has nine tabs: Pending, Saved, Archived, Dream, Graph, Policies, Evolution, Extraction and Sharing. Each saved memory shows its scope (user, project or session), whether it is pinned, its category and who proposed it.
The Graph tab has its own post: the memory graph. Pressing t in Memory opens an assistant that answers about the selected tab, category or memory.
Dream
Dream is the background job that reads recent conversations and proposes memories. It never edits files or runs commands. It runs when you ask (/dream) and, if you set a daily time, once a day for every project with a session updated in the last 24 hours.
What Dream reads
- Not whole transcripts: a digest of each of the project’s 12 newest sessions.
- The first request and the newest exchange that fits in 3,000 characters, never tool output or reasoning.
- The sentences where you corrected the agent or stated a rule, and test, typecheck or build results: at most 8 of each, 200 characters each.
- Secrets are redacted before anything is kept.
Every run stores a safety report: what it read, what it proposed and what became of it, what it refused, the secrets it redacted and the tokens it spent. The Dream tab shows it.
A side chat
Sometimes you want to ask about a session while it works. /btw <question> opens a side chat that answers about the current session without interrupting it. It can read files, search and run read-only commands such as git status or git diff, but it cannot edit.
/btw why did it pick the second migration?
Ctrl+] open, focus or close the side chat