Mistral Vibe: Sessions Open Faster With Cached Config, Cached Org Settings and Lighter History Reads
Mistral Vibe 3.0.4 made opening and resuming sessions faster in three ways. Vibe reuses the loaded config until a config file, trust decision or environment variable changes. It no longer waits for organization settings when a cached copy exists, and it reads only the latest history of a stored session.
Key Takeaways
- Mistral Vibe 3.0.4 reuses the loaded config until a config file, trust decision or environment variable changes.
- Sessions no longer wait for organization settings when a cached copy exists.
- Vibe checks for organization setting changes every 10 minutes in the background and retries failed checks after a delay.
- Opening a stored session reads only its latest history, which speeds up long sessions.
- Organization setting changes still reach open sessions at their next turn.
- The gains are most visible for resumed sessions and managed-settings environments.
Less Waiting at Startup
Mistral Vibe 3.0.4 targets the time between launching Vibe and being able to type. Three separate changes cut that wait.
Config Is Reused Until Something Changes
Vibe now reuses the loaded configuration and only reloads it when a config file, a trust decision or an environment variable changes. Sessions that start repeatedly in the same project no longer pay the full config-loading cost each time.
Organization Settings Are Cached
Opening or resuming a session no longer blocks on the organization's settings when a cached copy is available. Vibe checks for changes every 10 minutes in the background and retries a failed check after a delay. A change to organization settings reaches open sessions at their next turn.
Stored Sessions Read Only the Latest History
Opening a stored session now reads only its latest history, so long sessions open faster instead of loading everything that came before.
Why It Matters
Together, these changes make vibe --continue and session resume feel quicker, especially for long-running projects and users in organizations with managed settings.