Mistral Vibe: Built-in Git Worktree Support with --worktree

Mistral VibeJul 3, 2026

Mistral Vibe now ships a native --worktree NAME flag that creates or reuses a git worktree and runs the agent session inside it automatically. This removes the manual git worktree add + cd dance that developers previously had to script themselves to run multiple parallel Vibe sessions on isolated branches. It's aimed squarely at the increasingly common parallel agents workflow, where several coding-agent sessions work on different branches of the same repo without stepping on each other's working directory.

Native Worktree Management

Mistral Vibe introduced a --worktree NAME command-line option in version 2.19.0. Passing this flag tells Vibe to create a new git worktree (or reuse an existing one matching that name) and to start the agent session with that worktree as its working directory.

Previously, running multiple Mistral Vibe sessions in parallel on different branches of the same repository required manually creating worktrees with git worktree add, then launching Vibe separately inside each directory. That workflow was easy to get wrong: forgetting to cd into the right worktree, or losing track of which worktree corresponded to which task. With --worktree, Mistral Vibe handles the bookkeeping directly: name a worktree, and Vibe either spins up a fresh one or picks up where a previous session on that name left off.

Why It Matters for Parallel Agent Workflows

This lands at a moment when running several AI coding agents concurrently, each isolated on its own branch, has become a standard pattern for developers who want to explore multiple approaches or work on unrelated features simultaneously. By building worktree creation and reuse directly into the CLI invocation, Mistral Vibe lowers the setup cost for that workflow to a single flag, rather than requiring a wrapper script or manual git commands before every session.

Also in This Release

Version 2.19.0 also made the teleport URL clickable in the terminal, raised the context limit for the Leanstral theorem-proving integration, and disabled Sentry's automatic instrumentation integrations (crash reporting itself remains opt-in via enable_telemetry). Several stability fixes shipped alongside these changes, including moving path-prompt work off the UI thread and fixing a crash when submitting an empty multi-select question.