mistralai/mistral-vibe commit e607ccb, merged June 25 as v2.18.0, updated the changelog, package version, ACP setup docs, auth-status tests, fork-session tests, and provider API end-to-end tests.
For agent builders, the category consequence is narrow but useful: ACP compatibility is being treated as release work with executable checks rather than editor-integration copy. The caveat is equally clear: a release proves source behavior, not adoption.
Facts
- The 2.18.0 changelog says ACP gained a max-generated-tokens config option and fixed terminal kill/release bounding to prevent hangs.
- The Zed setup docs now point readers to the Mistral Vibe Zed ACP agent and the Agent Panel flow, replacing older extension and New Thread wording.
- The test suite adds fork-session coverage for inherited limits and updates auth sign-out checks to delete both the
ai.mistral.vibeand legacyvibekeyring entries.
Evidence
The strongest receipt is the release commit itself: one public merge ties version metadata, changelog claims, ACP setup text, and tests for session limits and credential cleanup into the same source snapshot.
Context
This is a Release-Claim Audit, not a claim that ACP has won a standard fight. The movement is that an agent client is making editor-facing protocol behavior inspectable at the same time it announces the release.
Limits
The evidence does not prove editor adoption, protocol completeness, or compatibility with every ACP client. Watch whether later Mistral Vibe releases keep ACP setup, auth, session limits, and hang prevention covered by tests and docs.