Grok Build gains cross-session project memory

xAI has added persistent memory to Grok Build, its coding agent, letting it carry conventions, decisions, and project facts across sessions instead of starting cold each time.

Capture runs in the background after every completed turn: Grok reviews the finished turn, writes anything durable as a markdown note, and continues without blocking the session. According to xAI, memory is scoped to what is likely to matter later — how a team writes and reviews code, decisions and the reasoning behind them, and facts such as where a subsystem lives or which command runs the test suite. Task state, tentative conclusions, secrets, and anything already covered by the repository or its docs are excluded.

Notes are stored per project, with a separate global set for preferences that apply everywhere. A /dream command folds recent notes into topic files — topics/testing.md, for example — so each project accumulates a small set of organized references rather than a sprawl of individual notes; dream also runs periodically on its own in the background. When a session resumes, Grok reads the topics covering the area it is about to work in. Instructions in the current conversation take precedence over anything stored in a note.

A /memory command opens a read-only browser of every memory file, grouped by scope, with a preview pane for inspecting or locating a note that needs editing.

The feature is live now and applies to new sessions only: users run /new or start a fresh grok, and notes begin accumulating after the first completed turn. xAI did not detail where notes are stored or how memory behaves across teams.