Browse memories with /memory in Grok Build

/memory (alias /mem) opens a read-only browser of every Build memory file so you can see what a session produced and find the file to fix when a note is wrong. Official Memory in Grok Build and Modes and Commands document the browser and the related shell commands.

Prerequisites

1. Enable memory in user config:

[memory]
enabled = true

in ~/.grok/config.toml / $GROK_HOME/config.toml, or export GROK_MEMORY=1. Walkthrough: Enable cross-session memory in Grok Build.

2. Work in a new session (/new or fresh grok) so capture and browse match the current product path.
3. Confirm /memory appears with /remember, /flush, and /dream in /help.

Open the browser

/memory

or:

/mem

The UI groups files by scope (workspace vs global) and shows a preview of the selected file. Use it after a few completed turns, after /remember, or when a later session follows a bad convention and you need to see which topic wrote it.

Fix one wrong note

1. Open /memory and select the topic that looks wrong (for example a testing or preferences file).
2. Note the file path the browser is showing.
3. Edit that markdown file on disk in your editor. The browser itself is read-only.
4. Return to Build and open /memory again to confirm the preview matches what you saved.

For a full wipe of a scope, use the CLI instead of deleting files by hand — Clear Grok Build memory from the CLI.

Related memory moves

Goal	Command / how-to
Save one explicit note	/remember <note> — Save a memory note
Write pending notes to disk now	/flush — Flush conversation memory
Merge raw notes into topic files	/dream — Run /dream
Understand what capture keeps	What Grok Build memory keeps

Pitfalls

• Without memory enabled, /memory / /mem do not appear.
• Instructions in the current conversation override stored notes — say the correction in chat when you need an immediate override without editing disk yet.
• Build memory is separate from consumer Grok memory on grok.com (Manage Grok memory).