Grok Build Rolls Out Persistent Cross-Session Memory

Starting September 16 (v1.0.34), xAI shipped persistent cross-session Memory for its coding agent Grok Build, eliminating the pain of re-explaining context in every session. Users sharing impressions on September 17–18 generally agreed the feature grows more useful with use.

Confirmed

• Core capability: Grok Build remembers codebases, commands, coding conventions, key decisions, reasoning and project facts across sessions, with per-project isolation
• How it works: after each conversation turn it silently reviews and records reasoned decision notes in the background without interrupting work; on returning to a project it reads these notes before touching related code instead of starting from scratch
• Storage: conventions and decisions are stored as Markdown topics that carry forward automatically, making them easy to inspect and audit
• Management: a new /memory command lets users browse what Grok Build remembers, alongside companion memory-management commands

Why it matters

• Cross-session memory is a key capability for coding agents. Users @XFreeze, @markk and @minchoi all noted it accumulates context the more you use it, substantially cutting repeated explanation costs
• Silent background recording preserves workflow continuity, and Markdown storage keeps the agent's memory transparent to users
• The feature fills an important gap in Grok Build's competition with rival coding agents

2026-09-17 ~ 2026-09-18 · 7 related posts

• [source] Grok Build adds persistent memory, remembering project conventions across sessions — XFreeze · 2026-09-17
• Grok Build Gains Memory, Learns From Your Workflow Over Time — mark_k · 2026-09-17
• Grok Build adds cross-session Memory: Markdown notes, per-project and global scopes — billyuchenlin · 2026-09-17

4 near-duplicate retellings: minchoi · minchoi · tetsuoai · tetsuoai