Forking creates another conversation path. Rewinding returns an existing session to a selected point using the capabilities available for its runtime. Neither operation should be treated as a general backup system.
#Fork an investigation
Use Fork on the relevant message when you want to explore another approach while keeping the original conversation.
- Find the turn containing the context you want.
- Choose its Fork action.
- Wait for the new session to appear.
- Check the copied history boundary and current provider.
- State the alternative task explicitly.
Example: “Explore an implementation without changing the public API. Inspect the current files before proposing edits.”
A fork is another conversation, not automatically a separate Git branch or worktree. Both sessions can still edit the same directory. Use worktrees when the alternatives need isolated files.
History boundaries depend on the runtime. Review what the new transcript actually contains, particularly around incomplete turns or provider-native task activity.
#Rewind a session
Stop active processing first. Where rewind is offered:
- Select Rewind on a turn, or enter rewind mode and select a message.
- Wait for the preview.
- Inspect the listed paths and diffs.
- Choose the offered conversation/file mode.
- Confirm only after checking the selected session and checkpoint.
- Inspect both the resulting transcript and working tree.
The preview distinguishes conversation-only behavior from file restoration. Conversation-only rewind leaves files unchanged. File restoration applies to the available recorded checkpoint and listed changes; it does not promise to undo every shell command, untracked file, external service action, or edit by another process.
A preview can report No file changes to restore or No diff available. Those messages are limits of the recorded evidence, not proof that the entire directory equals an earlier state.
#Recover cautiously
If rewind is unavailable, the provider or turn may lack a usable checkpoint. Preserve current changes and use Git or an explicit corrective edit instead.
If an operation errors or disconnects, inspect its observed result before retrying. Never assume rewinding a message recalls a sent email or reverts a remote deployment. See File history and Git, Stop and recovery, and Provider capabilities.