On June 16, mistralai/mistral-vibe shipped v2.16.1 with ACP workspace trust gated behind a workspace-trust client capability, one day after v2.16.0 added fuzzy slash-command search and syntax-highlighted, line-numbered edit diffs.
Facts
- Commit 564a143 adds workspace trust request handling in the ACP agent loop and tests for trusting a repo, trusting only a session, declining trust, and unsupported clients.
- Commit c2cb612 adds diff rendering tests, SSE parser tests, backend error handling tests, resume/session picker snapshots, and Mistral backend reasoning-output changes.
- The changelog lists scoped
/resume, inline clipboard confirmations, context-too-long classification, Free-plan banner display, and update-failure copy changes beside those code paths.
Evidence
The evidence shows release notes getting closer to runtime boundaries. Workspace trust is negotiated through ACP capability metadata. Diffs, SSE parsing, and reasoning-output behavior have dedicated tests instead of only a changelog sentence.
Context
For builders choosing agent tools, the practical question is not whether a release note sounds safer. It is whether the claim reaches code, tests, and protocol behavior that another client or operator can inspect.
Limits
The evidence does not prove the fixes work in every editor, terminal, or deployment. It shows Mistral's v2.16 line turning several claims into inspectable implementation and test surfaces.