Mistral Vibe
Operating Mistral Vibe on workers — the Mistral API key, programmatic mode, and why a missing key does not look like a failure.
Install
pip install mistral-vibeThe worker looks for vibe on the worker user's PATH.
Sign-in
Run vibe --setup once as the worker's user, or put MISTRAL_API_KEY in the task's environment profile.
Without a key Vibe opens its setup screen and exits with code 0 ("Setup cancelled"); the worker reports that as
authentication required, not as success.
How it runs
vibe --output streaming -p <prompt>
- Programmatic mode (
-p) approves all tools. - There is no model flag: the model comes from
~/.vibe/config.toml, so a task's model choice is not applied.
Add-on models
Mistral Vibe cannot use add-on models or providers configured on the worker. When it reaches its limit, the task moves to another compatible agent, or waits, as the fallback policy says.
Sessions
Resume is not claimed for Mistral Vibe: no resume command could be verified without an account. After a crash, recovery starts a fresh session from the checkpoint.
What was verified
Checked against Mistral Vibe 2.2.1 on 2026-10-06: its --help, and a real run without credentials through the
worker's session runtime. A task with the vendor's account has not been run.