Add the integration with Mistral Vibe cli

[0inp]

idea / problem

I'd like to have also an integration with Mistral AI Vibe CLI

requested change

Adding the integration with Mistral AI vibe CLI

why you want this

I want this because i'm using mistral ai vibe cli

[sfroment]

any news on that?

[emirbelkahia]

Consolidating here from #5111 (closed as duplicate), since this is the most upvoted thread. A few pieces of context that might help:

Earlier attempts. Two implementation PRs were opened and closed, as unsolicited PRs aren't accepted per CONTRIBUTING.md:

• feat: add mistral vibe agent integration #2226 (@sfroment): Agent::Vibe variant, vibe.toml manifest, session restore via Vibe's post_agent hook
• feat: add mistral vibe integration for state reports and session restore #4796 (@matapatos): state reports + session restore

#1883 also has a detailed feasibility write-up (process detection via the Python launcher, stable screen evidence for idle / working / blocked states).

Workaround for anyone waiting. HERDR_AGENT=claude vibe borrows Claude's manifest and gives approximate state tracking. It's inaccurate because Vibe's prompt, spinner glyphs and permission dialogs differ. Adding a post_agent hook in ~/.vibe/config.toml that reports idle back to herdr makes the idle state more reliable.

Useful hooks on the Vibe side. Vibe has a post_agent hook system and emits OSC title sequences, both of which could feed state reporting.

[perelin]

Another angle: companion apps are blocked on this too. Heeler (iOS client for herdr) launches agents via agent start --kind <kind>, and since vibe isn't in herdr's supported-kind list, it can't be offered there at all — Heeler deliberately only adds kinds once herdr supports them. So native Vibe support in herdr would unlock it for the whole ecosystem, not just the TUI.

[GitCroque]

+1, and the timing matters. With Mistral Large 4 out, Vibe is no longer a side experiment: it's becoming a main coding agent for a lot of people, especially in Europe, where client work often requires a European model (data sovereignty, GDPR).

I run Vibe next to Claude Code and Codex in herdr, and it's the only one that shows up as a plain terminal: no working/blocked/idle state, no notifications, no waits. The HERDR_AGENT=claude workaround above stays approximate, since Vibe's prompt and permission dialogs differ.

Native support would make herdr a first-class option for teams that mix a European model with the others.