Mistral Vibe: --continue Returns to the Last Session of the Current Terminal

Mistral VibeOct 30, 2026View original changelog

Mistral Vibe 3.0.4 restored vibe --continue so it reopens the last session of the current terminal in the current folder, not the folder's most recent session from any terminal. vibe -c -p now continues a session of the current folder rather than the latest one anywhere on the machine. A new VIBE_TERMINAL_KEY variable names the terminal.

Key Takeaways

vibe --continue again reopens the last session of the current terminal in the current folder.
The bug picked the most recent session from any terminal, which was confusing with multiple windows.
vibe -c -p now continues a session of the current folder, not one from anywhere on the machine.
VIBE_TERMINAL_KEY lets users name the terminal used by --continue.
An empty value makes --continue ignore the terminal.
The fix helps users running several terminals on one project.

Continue Means Continue Here

Mistral Vibe 3.0.4 fixed a behavior change that made vibe --continue surprising. It now reopens the last session of the current terminal in the current folder again. Before the fix, it picked the folder's most recent session from any terminal, which could pull in a session from a different window. For users who keep several terminals open on one project, this restores the expected one-terminal-one-session workflow.

Headless Continue Is Scoped Too

vibe -c -p now continues a session of the current folder instead of the most recent session anywhere on the machine.

Naming the Terminal

The new VIBE_TERMINAL_KEY environment variable names the terminal that --continue uses. Setting it to an empty value makes Vibe ignore the terminal and fall back to folder-based matching. This is useful for terminal multiplexers or scripts where the automatic terminal identity does not fit.