Mistral Vibe: Session Rename and Persistent Tool Permissions
Mistral VibeMistral Vibe v2.9.4 introduces the /rename command, allowing users to give custom names to their sessions directly from within the CLI for easier organization and recall. The release also adds "Always allow" permissions that persist across sessions, eliminating repetitive confirmation prompts for trusted tool calls. Additionally, bash bang commands (e.g., !ls) now execute asynchronously, and the underlying Mistral and Codestral SDKs have been bumped to their latest versions.
Session Organization Gets Easier with /rename
Mistral Vibe v2.9.4 adds a small but meaningful quality-of-life improvement: the /rename slash command. Users can now give any session a custom name from within the CLI itself, without leaving the conversation or editing configuration files manually. This makes it significantly easier to stay organized across multiple parallel sessions — especially for developers who regularly juggle several distinct tasks or projects simultaneously.
The feature fits naturally into the existing slash-command ecosystem and requires no additional configuration. Type /rename <name> and the session takes on that label, persisting it for future reference.
Persistent "Always Allow" Permissions
One of the more impactful changes in this release is the new "Always allow" permission persistence. Previously, when a user granted a tool permission during a session, that trust expired as soon as the session ended. In v2.9.4, permissions marked as "Always allow" now persist across sessions.
This change meaningfully reduces friction for experienced users who have already established trust with specific tools. Developers no longer need to re-confirm the same tool invocations every time they start a new session — Mistral Vibe remembers their preferences.
Security Consideration
The persistence is intentional and opt-in: only permissions explicitly granted as "Always allow" are retained. Standard one-time approvals continue to expire at session end, preserving the security model for users who want explicit control.
Asynchronous Bash Bang Commands
Bash bang commands — shorthand invocations like !ls or !git status — now execute asynchronously in v2.9.4. Previously these ran synchronously, which could create UI lag when the command took more than a moment to complete. The async execution keeps the interface responsive and brings bang commands in line with how other shell operations are handled within the agent loop.
SDK Bumps
The release includes updated dependencies for the Mistral SDK and Codestral SDK, keeping Mistral Vibe aligned with the latest API capabilities and bug fixes from the upstream libraries.
Bug Fix: /clear and Parent Session ID
A targeted bug fix addresses an issue where the /clear command was incorrectly carrying over the parent_session_id from the previous session. This caused sessions started after a /clear to be incorrectly linked as children of the prior session, which could produce unexpected behavior in session trees. The fix ensures that /clear properly resets session lineage.