xAI Adds Memory Feature to Grok Build to Maintain Conventions and Decisions Across Sessions

xAI has introduced a memory feature to Grok Build that maintains project context across sessions. This feature stores how the team writes code, technical decisions and their rationale, and permanent facts about the project (such as subsystem locations and test commands) to reduce repetitive explanations and improve work continuity.

Memory Storage and Exclusions

Memory is stored as Markdown files and organized by topic. It is managed separately under workspace scope (per project) and global scope (global preferences).

• Stored: How the team writes/reviews code, decisions and rationale, permanent project facts
• Excluded: Task status, tentative conclusions, secrets, content already included in repositories or documentation

How It Works: Capture and Recall

Memory capture runs in the background after each turn completes, without blocking the session. The /dream command allows merging new observations into the corresponding topic file, and this feature runs automatically in the background periodically.

Before starting work, relevant topic files are read to restore context. However, instructions in the current conversation take precedence over memory notes. The /memory command allows read-only navigation of all memory files grouped by scope, enabling verification of target files when correcting erroneous notes.

Application Examples and Availability

In a demo, after a cargo test failure in the ~/dev/orbit project led to an instruction to use just test, subsequent sessions recognized just test as the default test command, resulting in all 151 tests passing. When modifying src/webhooks.rs, memory-based test execution was also automated.

This feature is immediately available in Grok Build and applies to new sessions (/new or running a new grok). Note generation begins after the first turn completes.