1 hour ago
18
If you’ve ever had to re-explain your entire project to an AI coding assistant every time you start a new session, xAI just built the fix. Grok Build, the company’s CLI-based coding agent, now ships with a /remember command that lets users save notes and context that persist across sessions.
The feature landed as part of the v0.2.3 update on May 27, 2026, roughly ten days after Grok Build first launched in beta. It’s a deceptively simple addition that addresses one of the most persistent frustrations in AI-assisted development: the cold start problem.
What the update actually does
The /remember command lets developers store notes, preferences, and project context that carry over between sessions. Instead of telling your AI assistant “we’re using React with TypeScript, our API endpoints follow this naming convention, and here’s how our database schema works” every single time, you tell it once.
The update also bundles in a side-by-side preview feature alongside the saved notes, which means developers can see their stored context while working. But /remember isn’t the only thing in v0.2.3. The update also includes always-approve permissions, which lets users skip the confirmation step for trusted operations. Improved image processing capabilities made the cut too, along with JetBrains terminal support, which opens the door for developers who live in IntelliJ or WebStorm rather than VS Code.
The competitive landscape is getting crowded
xAI isn’t building Grok Build in a vacuum. Anthropic’s Claude Code has been carving out serious territory in the AI coding agent space, and Grok Build positions itself directly against that tool.
Early adopters have reported completing full-site builds in under an hour using Grok Build. Access to Grok Build requires a SuperGrok Heavy subscription at $300 per month.
Grok Build only entered beta on May 17, 2026. The fact that xAI shipped a meaningful feature update in just ten days signals an aggressive iteration cadence.
Why this matters beyond coding
xAI’s approach of using an explicit /remember command rather than passive memory accumulation gives developers control over exactly what gets retained, which matters in professional environments where you might work across multiple clients or projects with different conventions.
The risk is that Grok Build is still in beta, and the /remember feature specifically will need to prove it can handle the complexity of real-world projects without introducing confusion or stale context. A memory system that retains outdated architectural decisions could be worse than no memory at all.
Disclosure: This article was edited by Editorial Team. For more information on how we create and review content, see our Editorial Policy.
English (US) ·