Memory in Grok Build
Grok Build, xAI's coding agent, now keeps notes on how a project works and reads them back in later sessions. For people building software with Grok Build.

Details
- After each turn finishes, Grok reviews it in the background and saves anything durable as a markdown note: team conventions, decisions and why they were made, and project facts like which command runs the tests
- It leaves out task progress, tentative conclusions, secrets, and anything the repository's own docs already cover
- Notes are kept per project, plus a global set for preferences that apply everywhere
- The /dream command folds recent notes into one topic file per subject, and /memory opens a read-only browser of every memory file so you can find and fix a wrong note
- When you return, Grok reads the topics relevant to the code it is about to touch. Instructions in the current conversation override anything in a note
Best for
Ongoing projects where you keep correcting the agent on the same conventions or commands
When to use it
You come back to a project across many sessions and don't want to re-explain it each time
Who benefits
Developers and technical builders using Grok Build on the same codebase over weeks
Join the newsletter to get ahead with AI.
I share strategies, new modules, free guides, and tools to get you better at using AI in your work.
Leading a team? See team programs →