Illustration of an app window with two code panels, a violet Git branch splitting in two and a magenta shield with a check mark

Mistral Vibe Desktop: What It Is, Price, What to Check

Admin

Mistral AI released Vibe Desktop on November 17, 2026, an app for macOS and Windows that brings its work assistant and its coding agent together. The agent can read and edit a project's files on your own computer and run commands there. Linux support is coming later.

What we know

  • What it is: according to Mistral's November 17 release notes, Vibe Desktop combines work tasks, local coding sessions and cloud coding sessions in one app. Mistral tags it as generally available.
  • Local sessions: they run against a checkout of your repository on your machine. The documentation says the agent reads and edits files in that checkout and runs commands in your development environment.
  • Cloud sessions: they run in a sandbox hosted by Mistral, meant for when you don't have the project checked out locally.
  • Features: an integrated terminal, Git worktrees for parallel changes, background tasks, in-app code review and an integrated browser, per the release notes. You don't need to install the Vibe command-line tool first.
  • Approvals: the first-task guide says the agent may pause to ask approval for a command. It does not describe a separate approval for file edits: changes are reviewed afterwards in the Git changes panel.
  • Price: Mistral's product page lists a Free plan with no price, Pro at $14.99 a month and Team at $24.99 per user a month, excluding taxes, plus custom Enterprise. Pro and Team come with "fair usage" limits and no numbers. Neither that page nor the Desktop docs say which plan each session type needs.

What changes and what doesn't

What changes is where the agent works. Vibe was used on the web, in the terminal or inside an editor; now it has its own app that shows several tasks, their changes and their pull requests in one window.

What doesn't change is what needs watching. Mistral's own docs warn that an agent stopping does not mean a change is ready, and that creating or opening a pull request is not the same as merging it. They also warn that a worktree isolates files but not dependencies, environment variables or ports, and that two conversations on the same checkout share files.

How to tell if it affects you

It affects you if you, or whoever maintains your site, plan to run an AI agent on the site's code: a WordPress theme, Drupal modules or a custom build. Before your first local session:

  1. Work on a copy, never on the server. Open the session on a repository on your machine or a test environment, not on the live site's folder. Ask the agent to use a worktree or a new branch before editing.
  2. Keep secrets out of the repository. The agent reads the checkout: if your .env, wp-config.php or settings.php hold real production passwords, swap them for test-environment ones.
  3. Read every command before approving it. If the agent asks to run something that deletes files, touches the database or pushes to the server, stop and ask why.
  4. Review the diff file by file. Use the Git changes view (unified or split) and ask the agent to explain anything you didn't expect.
  5. Test before you publish. Run your tests or check the site on staging. Look hardest at what affects SEO: titles, canonicals, redirects, robots.txt and the sitemap.
  6. Let a person merge. If the agent opens a pull request, have someone merge it after reviewing it. Before paying, try a small task: Mistral doesn't say which plan covers each session type.

Related: Claude Code Approvals Leak Secrets to GitHub: What to Check

Sources

Updates: if Mistral ships the Linux version or clarifies which plan includes each session type, it will be added here with its link.

Worried about how this affects your website?
We will go over what to change with you. It is a free 30-minute call.