METAGROK
BUILD / what-grok-build-memory-keeps

Build

What Grok Build memory keeps

what-grok-build-memory-keeps

Grok Build memory stores durable project facts so later sessions can reuse them. Official Memory in Grok Build (Sep 16, 2026) describes background capture, markdown topic files, and read-back. Memory is off until you enable it — Enable cross-session memory in Grok Build.

Turn memory on, then start a new session

  1. Put this in ~/.grok/config.toml (or $GROK_HOME/config.toml):
[memory]
enabled = true

Or set GROK_MEMORY=1 / pass --experimental-memory for one run.

  1. Start a new session with /new or a fresh grok. Notes begin after the first completed turn. Older sessions already open do not pick up memory the same way.

  2. Confirm /memory, /flush, /dream, and /remember appear in /help.

What gets written

After each completed turn, Grok reviews the turn in the background and records durable details:

  • How the team writes and reviews code in this project
  • Decisions and the reasoning behind them
  • Project facts such as where a subsystem lives or which command runs the suite

Notes are markdown files. Each project has its own workspace scope. A separate global scope holds preferences that apply everywhere. Capture does not block the session.

What stays out

Memory leaves out task state, tentative conclusions, secrets, and anything the repository or its docs already cover. Keep tokens and private keys out of /remember notes as well. Put durable repo instructions in AGENTS.md when every session in the tree should load them — Make Grok Build follow AGENTS.md.

How later sessions use the notes

Before related work, Grok reads the topic files that cover the area. Instructions in the current conversation take precedence over anything stored in a note. Browse what landed with /memory — Browse memories with /memory. Fold a pile of raw notes into topics with /dream — Run /dream memory consolidation.

Build memory vs grok.com memory

This store is CLI Build only. Consumer chat memory on grok.com is a different control surface — Manage Grok memory. Grok Bot durable facts use Bot memory tools and files, not Build topic files.

Pitfalls

  • Project .grok/config.toml cannot enable [memory]; use user config under ~/.grok/.
  • Expect notes only after you enable memory and complete turns in a new session.
  • Do not treat every captured line as permanent policy — edit or clear wrong notes before they steer later work.