The CLI is oriented around Mistral's model path while exposing an agent interface to clients.
mistralai/mistral-vibe
A terminal coding agent whose ACP compatibility, release checks, packaging, and contributor boundaries make interoperability and maturity the strongest teaching surfaces.
Developers using a Mistral-backed coding workflow or an ACP-compatible client.
coding-agent CLI / ACP integration / release packages
Protocol compatibility is tested as a release contract
ACP support is tied to release evidence so compatibility is more than a capability claim in documentation.
System Map
Eight inspection boundariesRepository and session context are assembled for terminal coding work.
Coding tools act through the CLI runtime and can be surfaced through ACP.
The inspected evidence emphasizes compatibility and release boundaries; complete host enforcement remains an inspection question.
Protocol and release behavior provide the clearest public continuity contract.
Multi-agent delegation is not the strongest currently reported mechanism.
Terminal and ACP client surfaces mediate operator interaction.
Compatibility tests, releases, packaging, and contributor-visible changes provide the public receipts.
Learn Through This Project
7 lessonsLatest Reporting
3 articlesJune 26, 2026 — Mistral Vibe 2.18.0 turns ACP behavior, editor setup, auth cleanup, and fork-session limits into release-visible evidence. mistralai/mistral-vibe
Mistral Vibe Turns Release Claims Into Trust BoundariesJune 18, 2026 — The v2.16 release line says workspace trust, resume speed, diff rendering, SSE parsing, and backend reasoning behavior are no longer only UX claims; several now have code and tests behind them. mistralai/mistral-vibe
Mistral Vibe's Contributor Door Is Half OpenJune 13, 2026 — Mistral Vibe looks mature in release machinery and public feedback channels, but its own contributor guide keeps code contributions outside the main door for now. mistralai/mistral-vibe
Primary Sources
Open Questions
- Which compatibility claims remain stable across independent ACP clients and releases?
Evidence state describes what this Atlas profile can support today. It is not a product score and it is not evidence that uninspected capabilities are absent.