Grok Build adds memory across coding sessions
Project notes capture conventions and decisions, while current instructions retain precedence.
THE STORY IN THREE POINTS
- Grok Build memory was announced on September 16.
- Notes are stored as markdown with project and global scopes.
- The announcement says current conversation instructions take precedence.
The announcement
The Grok team announced memory in Grok Build on September 16. It says completed turns are reviewed in the background for durable conventions, decisions and project facts, which are stored in markdown topic files. Memory is scoped by project, with global preferences kept separately. The /memory command exposes the files and /dream organizes notes. Current instructions are described as taking precedence over remembered information.
Editorial context
Remembering the correct test command could save repeated explanation, while remembering an obsolete command could reproduce a mistake. The value of persistence depends on keeping notes inspectable and easy to correct. A useful memory system should support understanding why a later session made a decision, rather than making its behavior feel mysteriously personalized.
Editorial context: what to watch
A trial could alternate related projects, correct a deliberately stale instruction and check whether the next session follows the correction. It would also be useful to see how notes evolve after a repository changes substantially. These are suggested evaluation cases, not reported product defects; they test whether persistence improves the user’s actual development workflow over time.
Sources: Official Grok Build memory announcement, September 16 ↗
