Command reference Β· Antigravity CLI
/rewind
Rolls the conversation history back to a previous checkpoint. Alias: /undo.
/rewind (alias /undo) belongs to the "Conversations" category and resets your current conversation thread to an earlier, stable state. According to the best-practices docs, the typical use case is: if an agent has made several changes in a row that cause build errors, you don't need to discard the session β you type /rewind (or /undo) to return to the last working checkpoint. The history after that point is overwritten, not kept in parallel.
This clearly distinguishes the command from /fork (alias /branch): fork clones the current session at a stable point into a parallel session, to test risky changes there without losing the main history β if the attempt fails, /resume takes you back to the main branch. /rewind is a genuine backward move within the same thread, not a branch.
π THE SAME TASK (βUNDO CHANGES (UNDO/REWIND)β) ON OTHER PLATFORMS
β WHEN TO USE IT?
Undo several consecutive faulty changes by the agent
/rewind after the agent has made three edits that break the build β back to the last stable state
Rescue a session instead of restarting completely
/undo right after a botched change, instead of discarding the conversation and starting over
β WHEN NOT TO?
Trying an alternative approach in parallel to the existing history
/rewind overwrites the history from the chosen point onward, instead of keeping it as a branch.
Better: Use /fork (alias /branch) to start a parallel session from the stable state, and return with /resume if unsuccessful
SOURCES
- Antigravity CLI docs: command reference β antigravity.google
- Antigravity CLI docs: Best Practices β antigravity.google