Mistral Vibe: Choose Between Forking and Rewinding In Place
Mistral VibeMistral Vibe v2.23.3 upgraded the /rewind command to let users choose between forking a new conversation branch from an earlier point or rewinding in place, truncating the current session's history instead. Previously, rewinding always meant creating a new fork, even when a user simply wanted to discard recent turns and continue on the same session. The added choice gives developers finer control over how they manage conversation history when correcting course mid-task.
Key Takeaways
/rewindnow prompts users to choose between forking a new branch or rewinding in place in the current session.- Rewinding in place truncates the session's history after the chosen point instead of spawning a new conversation fork.
- Previously, every rewind action forced a fork, which could clutter session history with branches nobody needed to keep.
- The forking option is still available for cases where preserving the original conversation branch matters.
- The update builds on Rewind mode's existing ACP support for IDE integrations like VS Code, JetBrains, and Zed.
- Shipped in v2.23.3, released August 3, 2026, alongside related session-management improvements.
Two Ways to Go Back
Mistral Vibe's /rewind command lets users navigate back to an earlier point in a conversation, undoing recent turns to correct course after the agent goes down the wrong path. In v2.23.3, Mistral Vibe extended /rewind so that, when invoked, users are now asked to choose between two distinct behaviors: forking a new branch from the selected point, or rewinding the current session in place by truncating everything after it.
Why the Distinction Matters
Until this release, /rewind always forked — even when a user's intent was simply to discard the last few turns and keep working in the same session. That meant every correction produced a new conversation branch, which could clutter session history and make it harder to track which fork was the "real" one for a given task. With the ability to rewind in place, users who just want a clean do-over without spawning a new session identity can now get exactly that, while the forking option remains available for cases where preserving the original branch for later reference or comparison is actually desired.
A More Deliberate Rewind Workflow
The change effectively turns /rewind into a small decision point rather than a single fixed action, aligning it with how developers actually use it in practice: sometimes to branch and explore an alternative approach, and sometimes just to clean up a mistake and move on. It builds on Rewind mode's earlier expansion to IDE integrations via ACP, further rounding out the command as one of Mistral Vibe's core tools for managing long, iterative agent sessions.