Mistral Vibe: LLM Retries Now Visible in ACP & VS Code
Mistral VibeMistral Vibe now surfaces LLM retry status directly inside ACP-based IDE integrations, including VS Code, via a new _session/retrying protocol notification. Previously, when a backend LLM call failed and Vibe silently retried it, IDE users had no visual indicator and the agent panel could appear stalled. This shipped in v2.24.0 (2026-08-05), extending retry visibility that Mistral Vibe first introduced for the terminal UI and logs a few days earlier, and follows the same pattern the team has used to bring TUI-only features like teleport, rewind, and change review out to editor integrations.
Key Takeaways
- A new
_session/retryingACP notification now tells IDE clients exactly when Mistral Vibe is auto-retrying a failed LLM call, instead of leaving the panel looking frozen. - VS Code and other ACP-based editors (Zed, JetBrains via ACP) are the direct beneficiaries, since they previously had no signal at all for in-flight retries.
- This closes a gap left by the prior TUI-only retry visibility fix shipped just two days earlier in v2.23.3, which only reached the terminal UI and logs.
- The change follows an established rollout pattern at Mistral Vibe: ship a feature to the CLI first, then extend it to ACP/IDE integrations in a follow-up release, as previously done for teleport, rewind, and change review.
- v2.24.0 shipped alongside two other headline features — a "Default" unpinned model option and skill-loading for the Explore subagent — making retry visibility one of three notable user-facing changes in the same release.
- No independent third-party coverage exists yet for this feature, reflecting how fresh the release is (published 2026-08-05, four days before this check).
Retry Feedback Reaches the IDE
Mistral Vibe's v2.24.0 release closes a visibility gap for anyone running the agent inside an editor rather than the terminal. Earlier in the same week, Mistral Vibe introduced the /retry command and made LLM retries visible in the CLI's UI and logs, so terminal users could see when a request had failed and was being automatically retried instead of assuming the session had frozen. That fix, however, only reached the TUI — anyone running Mistral Vibe through the Agent Client Protocol (ACP), including inside the VS Code extension, still saw no feedback when a retry kicked in.
v2.24.0 fixes that by adding a dedicated _session/retrying notification to the ACP protocol. When a backend LLM call is interrupted and Mistral Vibe automatically retries it, ACP-connected clients now receive an explicit signal they can render in their own UI, rather than leaving the conversation panel looking stuck with no explanation.
Why It Matters for IDE Users
Silent retries are one of the more disorienting failure modes in agentic coding tools: the model call fails, the client retries behind the scenes, and from the user's seat nothing appears to be happening. Surfacing that state through a first-class protocol notification lets IDE integrations show a clear "retrying" indicator instead of a frozen or ambiguous loading state, which matters most during longer agent turns where a backend hiccup is more likely to occur mid-task.
This release continues a pattern Mistral Vibe has followed throughout 2026: ship a capability to the terminal first, then bring it to ACP-based editor integrations like VS Code and Zed once it has proven out. Teleport, rewind, and change review/approval all made that same jump from CLI-only to IDE-visible in prior releases, and retry status is the latest addition to that list.
Also Shipping in v2.24.0
The same release additionally introduced a "Default" (unpinned) model option and gave the Explore subagent the ability to load skills — both already documented separately. Alongside those, v2.24.0 added an admin config layer for shared and enforced configuration, minor autocopy interaction polish, and a handful of stability fixes, including a fix for /resume listing performance that no longer scales with total session count.