09/16/2026 | Press release | Archived content
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.
◆ Run cargo test
error: connection refused (postgres at localhost:5432) test result: FAILED. 143 passed; 5 failed; 0 ignored
❯ use just test, not cargo test. it starts the test database first.
◆ Run just test
Starting postgres on :5433 ... ready test result: ok. 148 passed; 0 failed; 0 ignored
All 148 tests pass with just test.
workspaces › orbit-3f9c2a1d › topics › testing.md
• Run the suite with just test . It starts the test database and then runs cargo test ; plain cargo test fails the integration tests.
• just test runs a single crate.
Fixtures• Integration tests seed from tests/fixtures/seed.sql .
❯ add a retry with backoff to the webhook sender
◆ Edit src/webhooks.rs
for attempt in 0..MAX_ATTEMPTS {
if self.post(event).await.is_ok() {
sleep(backoff(attempt)).await;
◆ Thought for 1.9s
The testing topic says the suite runs through just test.
◆ Run just test
Starting postgres on :5433 ... ready test result: ok. 151 passed; 0 failed; 0 ignored
Added the retry in src/webhooks.rs. 151 tests pass with just test.
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.
Stored as markdown
Notes are markdown files, one topic per subject. Each project has its own workspace scope, and a global scope holds preferences that apply everywhere. merges new observations into the topic they belong to, and shows the files as they are on disk.
Read back in later sessions
Before starting related work, Grok reads the topics that cover the area and applies them, including in sessions where the subject never comes up. Instructions in the current conversation take precedence over anything in a note.
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.
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.
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, 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.
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.
❯ add a retry with backoff to the webhook sender
◆ Edit src/webhooks.rs
◆ Thought for 1.9s
The testing topic says the suite runs through just test.
◆ Run just test
Starting postgres on :5433 ... ready test result: ok. 151 passed; 0 failed; 0 ignored
Added the retry in src/webhooks.rs. 151 tests pass with just test.
Enter :run │ Tab :complete │ Esc :clear
─ Memory ─
[✗]
MEMORY.md 1.2 KB · 2h ago
preferences.md 640 B · 2h ago
WorkspaceMEMORY.md 2.4 KB · 3m ago
testing.md 1.3 KB · 3m ago
code-style.md 1.1 KB · 2d ago
gateway.md 3.8 KB · 2d ago
9f2c4e1a-71b6-4d0e-8a3f-5c2d7b9e0f14__t000006-000006__n000.md 812 B · just now
• Reply preferences - How the user wants answers and PR descriptions written. ( topics/preferences.md )
↑/↓ nav │ / search │ y copy path │ x delete │ t toggle (on) │ ^F fullscreen │ Esc close
Memory is available in Grok Build now. It applies to new sessions: run or start a fresh , and notes begin after the first completed turn.