Mistral Vibe: Resumed Sessions Keep Their Agent
Mistral Vibe 3.0.1 changed session resume so that resuming or continuing a session keeps the agent it last ran on, even if the default agent has changed since. Sessions now record their agent, so one started with --agent reopens on that agent. Users switch agents inside the session to change it.
Key Takeaways
- Resuming or continuing a session now keeps the last-used agent.
- A changed default agent no longer overrides an older session's agent.
- Sessions record their agent, so
--agentsessions reopen correctly. - The change avoids surprise behavior or permission differences on resume.
- To switch agents, users change agents inside the session.
- This is a behavior change for anyone who relied on resume adopting the new default.
Resume returns you to the same agent
Mistral Vibe 3.0.1 changed what happens when a user resumes or continues a session. The session now keeps the agent it last ran on, even if the user's default agent has changed in the meantime. Previously, a changed default could silently swap the agent on resume.
Why it matters
Agents differ in their permissions and behavior, for example a cautious default agent versus an auto-approve one. Keeping the original agent avoids surprises when picking up older work. A related fix means sessions now record the agent they run on, so a session started with --agent reopens on that agent. To change agents after resuming, the user switches agents inside the session.