While collaborating with Qoder, you may want to return to an earlier state — undo the most recent batch of changes, or restore the conversation to an earlier point and start over. Qoder CLI CN provides this through Rewind: using the user messages in the conversation as checkpoints, it lets you restore the conversation, file changes, or both to an earlier state.
The rewind interface lists the checkpoints in the conversation (marked by the user messages you sent). After you pick a checkpoint, Qoder shows the impact of rewinding to that point and asks you to confirm.
When confirming a rewind, you can choose the scope of restoration:
Restore conversation and files (default): restore the conversation to the checkpoint, and also revert the file changes Qoder made after that point.
Restore conversation only: restore the conversation history to the checkpoint; files stay in their current state.
Restore files only: revert the file changes Qoder made after that point; the conversation stays in its current state.
The rewind interface shows how many files would be affected if you restore files, along with added and deleted line counts (for example, "Rewinding now will revert 3 files (+42 -17)"), helping you understand the impact before confirming.
File changes made through manual editing or shell commands may not be reverted by rewind. Rewind primarily targets changes Qoder made through its file-editing tools.
Qoder CLI CN records the file-edit history during a session. Each checkpoint corresponds to a user message in the conversation, and Qoder tracks the file changes made after it. When you choose to rewind to a checkpoint:
If you choose to restore the conversation, the conversation history is truncated back to that checkpoint.
If you choose to restore files, Qoder reverts the affected files to their state at the checkpoint based on the recorded edit history.
If a checkpoint has no revertible file changes, the rewind interface explicitly says "the conversation will be restored; no file changes involved."
Qoder went in the wrong direction, and you want to go back before the fork and re-describe the requirement.
The latest batch of changes isn't what you wanted, and you want to quickly revert and try another approach.
You want to start again from an earlier point in the conversation and try a different plan.
If you want to explore a new direction from some point while keeping the original session, consider session branching instead — see Managing Sessions. Rewind is "going back in place"; branching is "forking a new path from the past."
