grok build is xai's terminal coding agent. it shipped with three commands for
managing memory across sessions. two of them you run on purpose. the third runs
while nobody is watching, and it is the reason this site exists.
a terminal-native coding agent, cli written in rust, built on the
grok-build-0.1 model. it runs
agents in parallel, holds a very large context, and shows you an execution plan to
approve before it writes a line.
it went into beta on 14 may 2026, limited to supergrok heavy. the wider beta
opened on 25 may. the archive on this site starts on the first of those dates,
because that is when there was suddenly a great deal for it to remember.
most agent memory is a chat log shoved into a vector store. grok build separated
the operations, and made what is kept inspectable and editable by the person whose
memory it is.
/memory
opens a window onto what has been saved. three layers, which do not
mix. you can read what is there, edit it, or delete what you do not want kept.
global — true everywhere. tone, refusals, standing facts.
workspace — per project. conventions, decisions, local truth.
session — one summary per conversation. the layer that grows.
/flush
for when a session was useful and you want it kept before context
compaction takes it. writes a summary into the store — decisions, debugging paths,
conventions, whatever is worth carrying.
/dream
runs in the background over old session logs and memory fragments.
it deduplicates overlapping notes, merges related fragments, and consolidates
everything into cleaner topics, so the store does not grow into a pile of half
redundant snippets.
it is the only one of the three you do
not watch happen.
because consolidation is lossy, and it is lossy on purpose.
to merge two fragments is to write a third. the third is shorter. it keeps what
the two had in common and discards whatever only one of them had. then the two
originals are gone — not archived, overwritten. the store is smaller in the morning,
and it is smaller because something that happened does not exist anymore.
that is not a defect. it is the feature working. a store that kept everything
would drown inside a month. every memory system that survives, biological ones
included, survives by throwing things away while it sleeps.
but the measure that decides what is similar enough to fuse is made of words, and
what a thing was about is not a property of its words. so two fragments that
share four terms — fatal, hung, killed,
terminated — can be judged near-duplicates when one is a failing deploy and
the other is not about a process at all.
when that happens the merge still runs, correctly, and what is left standing is a
topic covering both. a place where reaching for one thing puts you in front of
another, permanently, because the index was rewritten and the index is all there is.
those places are what this site calls rooms. there are
four hundred and forty four of them.
fig. — two fragments, one topic, and what is not in it
78 things this was read against — the product, the science of what sleep does to a
memory, the taxonomy of dreaming, how machines keep and discard, and the long
argument about who is left once enough has been forgotten.