Mistral Vibe Desktop brings local and cloud coding into one app
Edited and reviewed by AI Ping Editorial Team
3-line summary
- Work and coding come together on macOS and Windows.
- Local sessions need no separate CLI installation; cloud sessions are another option.
- Changes, command output and pull requests can be inspected in the app.
Mistral released Vibe Desktop on November 17, combining Work with local and cloud coding sessions in one app for macOS and Windows. Developers can work on a project on their computer while following remote coding tasks and inspecting changes in the same window. The release brings Vibe’s productivity and coding modes together in a desktop interface.
The app requires no separate Vibe CLI installation. Mistral says local sessions share the command-line tool’s core agent engine and session logs, while Desktop does not embed or launch the CLI application itself. Tools and prompts can differ between interfaces. Existing terminal users gain a visual way to inspect files and command results alongside their conversations.
Work can use several local folders as context, including report directories in different locations. It shares conversations, projects, skills, connected tools and scheduled tasks with the web app. The documentation distinguishes making a directory available from reading every file into a conversation. Added folders can be cleared from the context list. Mistral illustrates this with a request to compare reports across two folders and cite the source files for each finding.
Two execution environments in one window
Local Code sessions use the repository checkout, shell and development environment on the user’s machine. They accommodate existing projects and tests requiring local dependencies. Cloud sessions clone a GitHub repository into a managed sandbox, where the agent runs commands and makes changes. Users choose the execution environment for the task.
The cloud workflow is designed for lengthy tasks that do not require keeping the computer open. When a remote session ends, sandbox files and build artifacts are deleted. Branches, commits and pull requests already saved to GitHub remain in the repository. Once the sandbox has been deprovisioned, continuing the work requires a new session. Its published cloud-session limits are 24 hours per session and three hours waiting for a reply, with limits subject to plan and rollout status.
Parallel work separates file isolation from conversation organization. Git worktrees share repository history while keeping working files in separate directories. Independent checkouts let tasks edit files without piling changes into the original working directory. Two conversations opened on the same checkout still share its files. Dependencies, external services and server ports may still require separate setup.
Sub-sessions handle independent tasks and send results to the main conversation. Delegated subagents have read-only views of their instructions, steps and findings. Further instructions go through the main agent.
Files, terminal output, reference pages and background commands belong to the selected conversation. Builds and development servers can continue while the conversation proceeds, with live output and status in their own panels. Stopping a conversation and stopping a background process are separate controls; a process panel provides the command’s Stop action. Agent summaries and actual command output remain separately inspectable.
Code review offers a unified view of removed and added lines or a split view with the before and after versions side by side. Users can open surrounding code, inspect pull request titles, numbers and status, and follow links in the integrated browser. Private repositories require a signed-in account with access there. Mistral’s guide keeps creating or opening a pull request separate from merging it, with changes and test output available for review.
Mistral’s pricing page lists limited coding sessions, messages and searches on Free. Before tax, Pro costs $14.99 monthly and Team costs $24.99 per user monthly, subject to fair usage. It does not separately map every Desktop capability to a plan. The release notes and Desktop guides list Linux support as coming soon, without a firm date.
Sources
- Vibe Desktop: Work and Code in one app — November 17 — Mistral AI
- Code on Desktop — Mistral AI
- Work on Desktop: local folder context — Mistral AI
- Vibe Code Web: remote sessions — Mistral AI
- Cloud-session limits and lifecycle — Mistral AI
- Desktop parallel tasks and worktrees — Mistral AI
- Follow and inspect work on Desktop — Mistral AI
- Review changes and pull requests — Mistral AI
- Current Mistral pricing — Mistral AI
- Choose CLI, VS Code, web, or Desktop sessions — Mistral AI
Corrections
- Changed the inline execution-environment diagram to a raster image so its labels render correctly.