Memory
Read what Ginu has learned, and say what it got wrong.
What this page covers
OutcomeFind a belief Ginu is working from, correct it, and see what the dreamer would change.
Before you beginHave a short conversation about a project or a working preference that matters beyond one reply.
Follow these steps
Memory is a tree of notes in files on your own disk: the conventions, decisions and preferences Ginu picked up while working with you. This screen reads them — adding, correcting and forgetting are things you say, not fields you fill in.
An (assumed) note is something Ginu inferred and has not confirmed with you. Find one about your active project and tell it whether the guess is right; “that’s wrong, it’s pnpm” is the whole interaction.
Lineage shows which older belief a note replaced and history shows every past edit to it, so a fact that changed is traceable rather than silently overwritten. An arrow marks a note imported from another CLI, and names the file it came from.
The dreamer, in the band below the tree, reads back through your session logs and folds what it finds into memory. It always asks before it runs, and anything needing your judgement arrives in Attention rather than landing unseen.
Example
That is wrong: use pnpm for this project. Remember the correction.
Open Memory and find the note. Its lineage shows the belief this one replaced, so a preference that changed reads as a history rather than as a contradiction.
Beliefs, not a transcript
Memory holds what Ginu concluded about your work, not what was said. Each note is a belief in a file you can open, and one marked “assumed” is an inference it has never checked with you — the label exists so you can tell a guess from something you told it.
Correcting one is a sentence: what is wrong, and what replaces it. Forgetting a fact and deleting old transcripts are different operations on different data, and the one you want is rarely both.
Run a memory pass with the dreamer
The dreamer looks back through session logs and other work context since its last pass. It looks for repeated conventions, useful decisions and notes that need consolidation. This is how a day’s activity can become durable context for another conversation.
Open Memory and find the dreamer band below the tree. Start a pass there and read the approval request before confirming: this operation rewrites memory.
After the pass, inspect the changes and review anything sent to Attention. A proposed change that needs your judgment waits for your acceptance. You can still correct a belief or ask Ginu to forget it.
“Let’s run the tests before we publish.”
“Keep the release note short.”
the memory pass
Run tests before publishing. Keep release notes concise.
See how it fits together
- 01Conversation
- 02Remembered context
- 03Your correction
- 04Updated context
Notes
- Memory is context Ginu keeps, not a record of everything said. It is not a promise that any particular detail comes back.
- Forgetting a fact and deleting transcripts are different actions on different data. Check which one you mean before running either.
Check
You can find a remembered fact, tell an assumption from a confirmed detail, and say how to correct or forget it.