After every completed turn the agent records conventions, decisions and project facts as markdown notes. Secrets, tentative conclusions and anything already documented stay out of memory, and an instruction in the conversation beats a note.
- Notes are kept per project, plus a global set for preferences that apply everywhere.
- /dream folds notes into topic files, /memory shows them read-only.
- Memory applies to new sessions started after the update.
“Run the tests with just test, not with cargo test.” You say it once. Then again the next day. And the day after that.
Grok Build so far was like a new colleague who comes in every morning with an empty head. Smart, fast and with no memory of yesterday at all.
Two things are done well and deserve to be said. Secrets stay out: the key, the database password and the token from the environment are kept out of the notes by rule. And the conversation beats memory, so an old note cannot shout down what you are saying now.
The third one is subtler. The notes are ordinary markdown files and you can open them. When the agent remembers something wrong, and it will, you know where to fix it. Memory you cannot see is more dangerous than no memory at all.
In a team it is worth opening /memory at the end of the first week and reading what the agent has decided it knows about you. You will learn something about the agent, and about the team.