xAI has launched memory for Grok Build, allowing the coding tool to carry team conventions, technical decisions, and durable project facts from one session to the next. Memory is available now, and note capture begins after the first completed turn; developers must run /new or start a fresh grok session for the saved context to apply. After every completed turn, Grok reviews the exchange in the background and records information likely to remain useful, without interrupting the active session. In xAI’s example, Grok initially runs cargo test, but the command fails because a PostgreSQL test database is unavailable; the user explains that just test should be used because it starts the database first, and Grok later follows that convention while the command is preserved in a testing note. The system stores notes as Markdown files, with one topic per subject. Project work stays within a dedicated workspace scope, while a global scope holds preferences that should carry across projects. The /dream command folds new observations into the relevant topic files, and xAI says the same process also runs periodically in the background. Users can open /memory to inspect the files in a read-only browser grouped by scope, with filtering, file previews, and controls to copy a path, delete a note, or switch one on or off. Before related work begins, Grok reads the relevant topics and applies them even when they are not mentioned in the new conversation, though instructions in the current conversation still take priority. The system retains code-writing and