Memory in Grok Build (2 minute read)

TLDR AI Tools

Summary

Grok Build now has a memory feature that automatically records project conventions, decisions, and facts to improve session continuity. It includes new commands for browsing and organizing memory notes.

Grok Build now includes memory, storing conventions, decisions, and project facts to improve future sessions.
Original Article
View Cached Full Text

Cached at: 09/17/26, 02:33 PM

# Memory in Grok Build Source: [https://x.ai/news/grok-build-memory](https://x.ai/news/grok-build-memory) Grok Build now has memory\. As you work, it keeps notes on the conventions, decisions, and project facts that come up, and later sessions read those notes before touching related code\. Grok Build gets better the more you use it\. ### Captured after the turn After a turn completes, Grok reviews it in the background and records anything durable: conventions, decisions, and project facts\. Capture runs on every completed turn and does not interrupt the session\. ## [What it remembers](https://x.ai/news/grok-build-memory#what-it-remembers) Memory holds the details most likely to matter in a later session: how the team writes and reviews code, decisions and the reasoning behind them, and durable facts about the project, from where a subsystem lives to which command runs the suite\. Task state, tentative conclusions, secrets, and anything the repository or its docs already cover are left out\. Notes are kept per project, plus a global set for preferences that apply everywhere\. ## [Written in the background](https://x.ai/news/grok-build-memory#written-in-the-background) Capture runs after a turn completes and never blocks the session\. Grok reviews the finished turn, writes anything worth keeping as a markdown note, and continues\. Over time,`/dream`folds those notes into topic files, one per subject, so each project ends up with a small set of organized references\. When you return to a project, Grok reads the topics that cover the area it is about to work in\. Instructions in the current conversation take precedence over anything in a note\. ## [Browsing memory](https://x.ai/news/grok-build-memory#browsing-memory) `/memory`opens a read\-only browser of every memory file, grouped by scope, with a preview of the selected file\. It is the fastest way to see what a session produced, and to find the file to edit when a note is wrong\. ## [New commands](https://x.ai/news/grok-build-memory#new-commands) - `/memory`opens the browser above\. - `/dream`organizes recent notes into topic files, for example`topics/testing\.md`\. Dream also runs on its own periodically in the background\. ## [Availability](https://x.ai/news/grok-build-memory#availability) Memory is available in Grok Build now\. It applies to new sessions: run`/new`or start a fresh`grok`, and notes begin after the first completed turn\.

Similar Articles

@RookieRicardoR: MemOS has made new progress. There are quite a few AI Memory solutions now, but many are still at the level of storing chat history. It looks like memory, but it's essentially adding a semantic search to markdown. @MemOS_dev has been working on a memory system for a while, from 1.0 all the way...

X AI KOLs Timeline

MemOS Local Plugin 2.0 update has been released, introducing the "Learn by Doing" feature, which allows the agent to convert key steps during task execution into reusable, scorable cognitive assets, thereby achieving continuous learning and memory in the local environment.

@mem0ai: https://x.com/mem0ai/status/2054580022049198513

X AI KOLs Timeline

This article explains how memory works in Codex CLI, OpenAI's open-source coding agent. It describes the memory architecture based on markdown files, the write path with phased extraction and consolidation, and the read path using keyword search, all designed for predictability and low retrieval cost.

Memoriq

Product Hunt

Memoriq is a private AI memory service that works across ChatGPT, Claude, Gemini, and Grok.

@mem0ai: https://x.com/mem0ai/status/2064383137338233179

X AI KOLs Timeline

This article analyzes GitHub Copilot's memory architecture, which uses structured memory objects anchored to specific code citations and employs just-in-time verification to combat knowledge staleness. With memory enabled, Copilot's pull request merge rate improved from 83% to 90% in an A/B test on real developers.