Mistral Vibe: Self-Hosted Setups Stop Contacting Mistral, and Project Config Can't Re-Enable Telemetry
Mistral Vibe no longer contacts Mistral's experiment service or sends crash reports when a Mistral provider's api_base is outside mistral.ai, as in self-hosted deployments. A project's .vibe/config.toml or agent profile can also now turn telemetry off but never back on.
Key Takeaways
- Self-hosted setups no longer reach Mistral's experiment service or crash reporting.
- Voice features follow the provider's api_base.
- Project config cannot enable telemetry.
- An ignored
enable_telemetry = trueproduces a warning. - Projects can still turn telemetry off.
- It protects data-sensitive and air-gapped environments.
Self-hosted deployments stay self-contained
When a Mistral provider's api_base is outside mistral.ai and its subdomains, Vibe no longer contacts Mistral's experiment service and no longer sends crash reports to Mistral, even with telemetry on. Voice dictation and read-aloud now use the server at the provider's api_base rather than api.mistral.ai (except api.eu.mistral.ai and api.us.mistral.ai, which keep api.mistral.ai), unless transcribe_providers or tts_providers set another address.
Telemetry can only be tightened by a project
A project's .vibe/config.toml or an agent profile may turn usage telemetry off but can no longer turn it on. Its enable_telemetry = true is ignored with a warning, so a cloned repository cannot opt a user into telemetry.