Mistral Vibe: New /branch Command for Session Forking
Mistral VibeMistral Vibe added a /branch command in v2.25.3 that forks the active conversation into a brand-new, independently resumable session while leaving the original untouched. Developers can pick up the forked copy in another terminal with vibe --resume <id>, making it easy to explore an alternative approach or hand off context without disrupting ongoing work. The feature complements Mistral Vibe's existing /rewind and worktree tooling rather than replacing them.
Key Takeaways
/branchforks without disruption, cloning the full conversation history into a new session id while the original session keeps running untouched.- Resumable anywhere, with
vibe --resume <id>letting the forked copy be picked up in a different terminal, machine, or by a teammate. - Complements, not replaces,
/rewind, since forking preserves history rather than truncating it, giving developers a non-destructive alternative for course-correcting. - Pairs with worktree tooling, so a branched conversation can move into its own git worktree and let two lines of exploration run in parallel on disk.
- Ships in v2.25.3, released September 11, 2026, alongside Git-aware
@file mentions and a session-log permissions fix. - Addresses a real workflow gap, where developers previously had to interrupt a live session or manually rebuild context to explore a second approach.
New /branch Command
Mistral Vibe introduced a /branch command in version 2.25.3, giving developers a lightweight way to fork the current conversation into a brand-new, independently resumable session without disturbing the session already in progress. Typing /branch clones the conversation's state, including its history up to that point, into a new session id, while the original session keeps running exactly as before.
Why It Matters
Long agent sessions often reach a fork in the road: a developer wants to try a risky refactor, explore an alternative approach, or hand a copy of the current context to a teammate, all without losing the working session they already have. Before this release, doing that meant either interrupting the live session with /rewind, which could truncate history, or manually re-creating context in a fresh session. /branch sidesteps both trade-offs: it captures a full snapshot and moves on, leaving the current terminal session unchanged.
How It Works
The forked copy is resumable from any terminal with vibe --resume <id>, so a developer can keep working in the original window while continuing the branched conversation elsewhere, whether that is a second terminal tab, a different machine, or a teammate's own environment once the id is shared. This pairs naturally with Mistral Vibe's existing worktree tooling, letting a forked conversation move into its own git worktree so two lines of exploration can proceed on disk as well as in conversation history.
Also in This Release
Version 2.25.3 shipped alongside two related quality-of-life changes: @ file mentions now use Git-aware discovery and accept standalone pasted files and folders, and new session log files are no longer readable by other users on POSIX systems (each covered in Mistral Vibe's own dedicated entries).