Memory in Grok Build

What changed

Source summary

xAI added persistent memory to Grok Build: it automatically captures project conventions, decisions, and facts as markdown notes (per-project and global) after each turn, and reads relevant notes back in on future sessions via new /memory and /dream commands. Task state, tentative conclusions, secrets, and anything already covered by the repo or its docs are deliberately excluded, and instructions in the live conversation always override stored notes. It applies to new sessions (run /new to pick it up).

Why it matters to your work

Practical interpretation

If you use Grok Build for coding projects, it now remembers your project's conventions and past decisions between sessions instead of starting from scratch each time, saving you from re-explaining context. It only kicks in on new sessions, and it deliberately will not store secrets or things already documented in your repo.

When this could help

Returning to an existing codebase in a new Grok Build session, or working on a project over many sessions where setup quirks and conventions keep recurring

Grok Build now writes background notes on project conventions, testing commands, and decisions after each turn, then reads them back in on later sessions so you don't have to re-explain the same context every time

How to get started

1. Install Grok Build using the installer script from https://x.ai/cli/install.sh

   Provider guidance ↗

2. Start a fresh session with /new (or a new grok session) — memory only applies to sessions started after it is enabled

   Provider guidance ↗

3. Work as normal; after each completed turn Grok reviews it and writes durable notes to per-project and global markdown files in the background

   Provider guidance ↗

4. Run /memory to open a read-only browser of the stored notes, grouped by scope, with a preview

   Provider guidance ↗

5. Run /dream to merge recent observations into the matching topic files (it also runs periodically in the background)

   Provider guidance ↗

Build it into your routine

SCALA suggested workflow

1. Resuming a project after time away

   Start a new Grok Build session and have it recall prior testing commands (e.g. using just test instead of cargo test) and project conventions without being told again.

2. Checking what Grok has learned

   Run /memory periodically to review what has been captured and correct anything wrong before it is relied on in future sessions.

What to check

• Memory only applies to new sessions — sessions already running will not pick up the feature Source ↗
• Instructions given in the live conversation always override anything stored in a note Source ↗
• Deliberately excludes task state, tentative conclusions, secrets, and anything already covered by the repo or its docs Source ↗