Pre-submit Checks
Describe the solution you'd like?
Add Mistral Vibe to Warp's list of recognized CLI agents so running vibe (interactive TUI) or vibe-acp (ACP-mode binary) in a Warp pane is detected as a known agent on par with Claude Code, Codex, Gemini CLI, OpenCode, etc.
Mistral Vibe is the open-source ACP-compatible CLI shipped by Mistral AI alongside Devstral 2 (Dec 2025). It is Apache 2.0 licensed, installable via uv tool install mistral-vibe or pip install mistral-vibe, and supports any OpenAI-compatible model endpoint — Mistral cloud (Devstral 2 / Devstral Small 2), vLLM, MLX, llama.cpp.
The change is purely additive and follows the existing pattern. Specifically, in app/src/terminal/cli_agent.rs:
- Add a
Vibe variant to enum CLIAgent (around line 116).
- Complete the exhaustive matches that already enumerate the other agents:
command_prefix → "vibe" (the user-facing entry point; vibe-acp is an alternative the CLI also exposes).
display_name → "Mistral Vibe".
icon → a new Icon::MistralLogo (or initially None for a draft PR).
brand_color → Mistral's orange (e.g. #FA520F).
brand_icon_color → white.
supported_skill_providers → &[SkillProvider::Agents] to start; mistral-vibe also has a native skill loader (skill_paths in ~/.vibe/config.toml) which could become a dedicated SkillProvider::Vibe later.
supports_bash_mode → defaults to false; can be enabled in a follow-up.
- Add the brand color constant (e.g.
MISTRAL_ORANGE) and the icon asset.
- Optionally: a minimal
vibe.rs plugin manager in app/src/terminal/cli_agent_sessions/plugin_manager/ returning can_auto_install() = false and providing manual install instructions (uv tool install mistral-vibe). This is not required for basic recognition — is_installed() defaults to false in the trait — but it makes the install footer behave like the other agents.
No new protocol or transport code is needed: vibe-acp already speaks ACP, and vibe itself is a regular interactive terminal process that Warp's blocks/editor already wrap.
Is your feature request related to a problem? Please describe.
Today, vibe runs fine in a Warp pane but Warp doesn't recognize it as a CLI agent, so users miss out on:
- The CLI agent toolbar.
- The brand-colored icon in the harness selector.
- Skill-provider integration.
- Agent-mode session telemetry / session sharing.
Mistral's Dec 2025 Devstral 2 release (123B, SWE-bench Verified 72.2%) and Devstral Small 2 (24B, 68.0%) are competitive open-weight coding models, and Mistral Vibe is the maintained open-source CLI for them. Adding it to the recognized list brings open-weight coding agents into parity with the closed-source agents Warp already supports, which fits Warp's stated multi-model / multi-harness direction.
Additional context
Pointers from a brief read of the open-source repo on master at 2026-04-30:
- Central enum:
app/src/terminal/cli_agent.rs:116 — enum CLIAgent with ~7 exhaustive matches that need new arms (the WARP.md rule against wildcard _ makes this mechanical but tedious; same shape as other agent additions like Auggie/CursorCli/Goose).
- Plugin manager pattern:
app/src/terminal/cli_agent_sessions/plugin_manager/{claude,codex,gemini,opencode}.rs — straightforward to mirror.
- Estimated diff: ~10-15 additive lines + match-arm completion across ~7 sites + one icon SVG/PNG. Optional plugin_manager file would add ~30-50 lines.
Mistral Vibe / Devstral 2 references:
Happy to draft the PR once this issue receives a ready-to-implement label, per CONTRIBUTING.md.
Operating system (OS)
macOS
How important is this feature to you?
3
Warp Internal (ignore) - linear-label:39cc6478-1249-4ee7-950b-c428edfeecd1
None
Pre-submit Checks
Describe the solution you'd like?
Add Mistral Vibe to Warp's list of recognized CLI agents so running
vibe(interactive TUI) orvibe-acp(ACP-mode binary) in a Warp pane is detected as a known agent on par with Claude Code, Codex, Gemini CLI, OpenCode, etc.Mistral Vibe is the open-source ACP-compatible CLI shipped by Mistral AI alongside Devstral 2 (Dec 2025). It is Apache 2.0 licensed, installable via
uv tool install mistral-vibeorpip install mistral-vibe, and supports any OpenAI-compatible model endpoint — Mistral cloud (Devstral 2 / Devstral Small 2), vLLM, MLX, llama.cpp.The change is purely additive and follows the existing pattern. Specifically, in
app/src/terminal/cli_agent.rs:Vibevariant toenum CLIAgent(around line 116).command_prefix→"vibe"(the user-facing entry point;vibe-acpis an alternative the CLI also exposes).display_name→"Mistral Vibe".icon→ a newIcon::MistralLogo(or initiallyNonefor a draft PR).brand_color→ Mistral's orange (e.g.#FA520F).brand_icon_color→ white.supported_skill_providers→&[SkillProvider::Agents]to start;mistral-vibealso has a native skill loader (skill_pathsin~/.vibe/config.toml) which could become a dedicatedSkillProvider::Vibelater.supports_bash_mode→ defaults tofalse; can be enabled in a follow-up.MISTRAL_ORANGE) and the icon asset.vibe.rsplugin manager inapp/src/terminal/cli_agent_sessions/plugin_manager/returningcan_auto_install() = falseand providing manual install instructions (uv tool install mistral-vibe). This is not required for basic recognition —is_installed()defaults tofalsein the trait — but it makes the install footer behave like the other agents.No new protocol or transport code is needed:
vibe-acpalready speaks ACP, andvibeitself is a regular interactive terminal process that Warp's blocks/editor already wrap.Is your feature request related to a problem? Please describe.
Today,
viberuns fine in a Warp pane but Warp doesn't recognize it as a CLI agent, so users miss out on:Mistral's Dec 2025 Devstral 2 release (123B, SWE-bench Verified 72.2%) and Devstral Small 2 (24B, 68.0%) are competitive open-weight coding models, and Mistral Vibe is the maintained open-source CLI for them. Adding it to the recognized list brings open-weight coding agents into parity with the closed-source agents Warp already supports, which fits Warp's stated multi-model / multi-harness direction.
Additional context
Pointers from a brief read of the open-source repo on
masterat 2026-04-30:app/src/terminal/cli_agent.rs:116—enum CLIAgentwith ~7 exhaustive matches that need new arms (theWARP.mdrule against wildcard_makes this mechanical but tedious; same shape as other agent additions like Auggie/CursorCli/Goose).app/src/terminal/cli_agent_sessions/plugin_manager/{claude,codex,gemini,opencode}.rs— straightforward to mirror.Mistral Vibe / Devstral 2 references:
Happy to draft the PR once this issue receives a
ready-to-implementlabel, perCONTRIBUTING.md.Operating system (OS)
macOS
How important is this feature to you?
3
Warp Internal (ignore) - linear-label:39cc6478-1249-4ee7-950b-c428edfeecd1
None