Flush conversation memory to disk in Grok Build

/flush is a shell-provided command that writes conversation memory to disk now. It only appears when cross-session memory is enabled. Official: Modes and Commands.

Prerequisites

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.

Confirm /flush shows in /help or the palette with /remember, /memory (alias /mem), and /dream. Full enable steps: Enable cross-session memory in Grok Build.

Flush now

In a Build session with memory on:

/flush

Use /flush when you just captured something with /remember and want it on disk before you quit, switch projects, or run /dream. Closing the TUI without a flush can leave the latest notes unwritten until the client’s normal write path runs.

Related memory commands

Command	What it does
/remember <note>	Save a memory note — Save a memory note with /remember
/memory / /mem	Browse and manage stored notes — Browse memories with /memory
/dream	Consolidate stored notes — Run /dream

Pitfalls

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