1. The early messages are still in the room
A session feels like a notebook that grows forever. The model does not experience it that way. Everything still in the window competes with the current task: the first attempt, the error you already fixed, the log you pasted, the argument about a design you rejected.
Past a point, answers get sloppy. Grok “forgets” a constraint that is still in the chat, because the constraint is buried. The fix is not a louder reminder. The fix is less history.
2. Compact is a summary, not a recording
Type /compact when the early turns no longer matter. Grok compresses the history so the window has room again. It may also compact on its own when the window is nearly full, and it tells you when that happens.
A summary drops detail. That is what a summary is. A number, a file path, or a “do not touch this” line can disappear. Before you compact, make sure the finish line and the approach live in a file. The plan file for this session is one place. A short note in the repository is the place a new session can see. The chat is not the archive.
On the invoice button, the finish line was the column order and the untouched API. After a compact, the session may still remember “add a download” and lose “Date, Vendor, and Amount, in that order.” The plan file for this session still has the order. Open it with /view-plan, or copy the line into the repository, and point the next prompt at the copy. Do not hope the summary kept it.
3. A new session is a clean desk
/new starts a fresh session. /resume opens a picker of recent ones. From the shell, grok -c continues the most recent session in this directory. Use a new session when the task has changed. Carrying a refund bug into a documentation edit brings the refund bug’s debris with it.
Start the new session by pointing at a file in the repository, not by retelling the novel. The session plan does not come along by itself. Copy the finish line first. “Read docs/invoice-plan.md. Implement only the must-work section. The tests to run are in AGENTS.md.” The handbook and that file are why a fresh session is not amnesia.
4. Rewind puts the chat back. The files stay.
/rewind (also /undo) drops later turns and returns the conversation to an earlier prompt. The files on disk stay as they are. If Grok edited ten files and you rewind the chat, those edits are still in the files.
Older versions of Grok Build also put files back on a rewind. Current versions do not. Check the diff before you assume either way. That surprise is the whole lesson. Rewind is for a conversation that went down a bad path, when you want to ask again from an earlier moment. It is not an undo button for the project. If you need the files back, use the project’s own history, usually git, and look at the diff first.
5. Memory is a notebook, and it is off
Grok has a separate memory feature. It is experimental, and it is off unless you enable it. When it is on, it stores short markdown notes for later sessions. It does not store a transcript of every chat. A new session still will not know what you said yesterday unless a note was saved, or unless the fact is in AGENTS.md.
Leave memory off until you have a reason. The handbook in the repository is the memory your teammates can see and edit. The next page is for when one session is not enough: several workers, with one owner each.