Mistral Vibe Code

Mistral AI

★★★★☆

Mistral's coding agent across terminal, IDE, web, remote sessions, and configurable models.

Category coding-assistant
Pricing Included with eligible Vibe plans subject to usage limits; pay-as-you-go API access and local or compatible-provider routes use separate billing and configuration.
Status active
Platforms macos, linux, windows, vscode, jetbrains, zed, web
mistral vibe coding-assistant cli agentic skills subagents remote-agents local-models acp
Updated July 10, 2026 Official site →

Overview

Freshness note: AI coding tools change rapidly. This profile is a point-in-time snapshot last verified on July 10, 2026.

Mistral Vibe Code is the developer surface inside the broader Mistral Vibe product. It now spans the terminal, VS Code, JetBrains and Zed through ACP, a dedicated web surface, and remote/background agents. “Vibe CLI” no longer describes the whole product.

The terminal route remains central: Vibe explores repositories, edits files, runs commands, and works across multi-file tasks from the project root. The newer surfaces add editor-native work, isolated remote sessions, parallel tasks, and a one-way handoff from a live local CLI session into cloud execution.

Key Features

Vibe Code supports file and code search, edits, shell commands, git inspection, planning, tests, and reviewable diffs. Skills turn recurring instructions into reusable commands, while custom modes and subagents let teams route specialized work inside a session. Session-scoped permissions can ask, allow, or deny access for commands, files, and directories.

The IDE and remote-agent layers broaden the workflow. Mistral documents native editor experiences, GitHub/GitLab/Jira context, async agents, isolated web sessions, and pull-request handoff. The /teleport command moves an active CLI session into Vibe Code Web with its history and branch state, but the handoff is one-way: the session cannot return to the local CLI and must continue on the web.

Teleport is currently part of the Vibe Code Web Public Preview. It requires an API key tied to a Pro, Team, or Enterprise account, the Mistral GitHub App installed for the working repository, a CLI session launched inside a Git repository, and a Mistral model selected locally. Third-party-model sessions cannot be teleported, and the cloud session runs on Mistral Medium 3.5.

The CLI also retains flexible model routing. Users can authenticate with a Mistral plan, configure a Mistral API key, or use documented local/offline and compatible-provider routes. Current Mistral model guidance points new agentic and coding evaluations toward Mistral Medium 3.5 rather than deprecated Devstral 2, although product pages still mention several coding-model options.

Strengths

Vibe Code is strongest for developers who want one coding agent across local and delegated work without being locked to one interface. Terminal control, editor access, remote execution, skills, and configurable routing cover a wider operating range than a simple autocomplete extension.

The approval and handoff model is also practical. Teams can keep risky commands reviewable, inspect diffs before merge, and choose whether a task should remain local or continue remotely.

Limitations

The breadth creates configuration complexity. CLI, editor, remote-agent, API-key, subscription, and local-model routes do not have identical billing, privacy, performance, or availability. Teams should standardize one route before documenting Vibe as a shared workflow.

Local or self-managed model support is not a blanket privacy guarantee for every Vibe surface. Verify where the model runs, which connectors are active, what leaves the repository, and how remote sessions retain data. Model defaults and older Devstral wording also continue to move, so pin and test the route you depend on.

Practical Tips

Begin in the CLI with approval prompts enabled and one bounded repo task. Add a reusable skill only after the workflow works reliably by hand. Use remote agents for reviewable background work, not as a reason to weaken branch, test, or merge controls.

Choose a model preset deliberately. Mistral Medium 3.5 is the current Mistral-native starting point for demanding agentic coding; local models are useful when deployment control matters more than peak capability. Keep Mistral Studio separate: it is the platform for custom production agents and governed assets, not the day-to-day coding interface.

Verdict

Mistral Vibe Code has grown from a promising CLI into a credible multi-surface coding agent. It is worth considering when terminal control, IDE integration, remote sessions, and flexible model routing matter more than committing to a single closed coding stack.