Run /dream memory consolidation in Grok Build

/dream is a shell-provided command that consolidates cross-session memory. It only appears when memory is enabled. Official: Modes and Commands and Settings reference.

Prerequisites

1. Turn memory on in user config (~/.grok/config.toml or $GROK_HOME/config.toml):

[memory]
enabled = true

Or for one process: export GROK_MEMORY=1. Single-run CLI flags: --experimental-memory / --no-memory.

2. Confirm the memory commands show in /help or the palette: /remember, /flush, /memory (alias /mem), and /dream.

Full enable steps: Enable cross-session memory in Grok Build.

Run consolidation

In a Build session with memory on:

/dream

Use /dream when you want the client to consolidate stored notes — after a long session, before switching projects, or when /memory shows a pile of raw notes you want compressed. Save a single note with /remember <note> first if the fact is not on disk yet. Force a write with /flush if you just captured something and want it on disk before consolidation.

Clear when you need a clean slate

From the shell (outside the TUI if needed):

grok memory clear --workspace
grok memory clear --global
grok memory clear --all

Pitfalls

• Without [memory] enabled / GROK_MEMORY=1, /dream does not appear — enable memory first.
• Project .grok/config.toml does not own [memory]; put it in user config under ~/.grok/.
• /dream consolidates Build cross-session memory. It is not consumer Grok memory on grok.com (Manage Grok memory).