Grok Build adds memory across coding sessions
Grok Build now records project conventions, decisions, and facts in the background, then reads relevant notes in later sessions. Notes are stored as markdown and can be browsed or organized with commands.
SessionWatcher editorial · Published · Updated · Source announcement: 2026-09-16
Memory carries project context forward
xAI announced Memory in Grok Build on September 16, 2026. As work proceeds, Grok Build records conventions, decisions, and project facts in the background, then reads relevant notes before working on related code in later sessions.
The notes are markdown files scoped to a project, with a separate global scope for preferences. Capture runs after a turn completes; the announcement says it does not interrupt the session.
Sources: Memory in Grok Build
Inspect and organize saved notes
Use `/memory` to browse memory files in read-only mode. The announcement also describes `/dream` as merging observations into topic files, and says it runs periodically on its own as well as when invoked.
The feature is for durable context such as coding conventions and project facts. The announcement says task state, tentative conclusions, secrets, and information already covered by repository or documentation are left out. It also says instructions in the current conversation take precedence over saved notes.
Sources: Memory in Grok Build
When memory becomes available
Memory is available in Grok Build and applies to new sessions. Start a fresh session with `/new`; notes begin after its first completed turn.
Sources: Memory in Grok Build
AI assisted reporting, checked against the linked official sources. Source pages checked 2026-09-30. Editorial process and corrections.