Skip to main content
Lesson 2 of 16 · Mistral Vibe: AI Coding CLI

Install Mistral Vibe CLI

Lesson 2 of 16 Updated November 2, 2026 Developer
On this page
  1. Prerequisites
  2. Installation on Mac and Linux
  3. Installation on Windows
  4. Verify the Installation
  5. Troubleshooting Common Issues
  6. Key Takeaways

Prerequisites

Before installing Vibe, ensure your system has Python 3.12 or higher. This is the only mandatory technical dependency, and it’s also the most common source of failure: many Linux machines still ship with Python 3.10 or 3.11 by default. Start by checking your version:

python3 --version
# or on some systems
python --version

If you see a version lower than 3.12, update Python from the official website or via your package manager. Do not proceed until you fix this: an installation launched on an older version fails with a dependency resolution error that doesn’t indicate the real cause.

Installation on Mac and Linux

The fastest method on Mac and Linux is the official installation script. A single command is all you need:

curl -LsSf https://mistral.ai/vibe/install.sh | bash

This script detects your system, installs uv—the ultra-fast Python package manager—if necessary, and then installs Vibe as a global tool. Once finished, the vibe command is available in your terminal.

Alternative with uv

If you already use uv, you can install Vibe directly without running the script:

uv tool install mistral-vibe

uv automatically handles the virtual environment and dependencies. This is the preferred method if you work on multiple Python projects and want to avoid conflicts: Vibe lives in its own isolated environment and will never overwrite a library version that one of your projects depends on.

Alternative with pip

For a classic installation via pip:

pip install mistral-vibe

This works, but it installs Vibe into the current Python environment, carrying the risk of collisions. If you encounter dependency conflicts, isolate the tool in a dedicated virtual environment:

python3 -m venv ~/.vibe-env
source ~/.vibe-env/bin/activate
pip install mistral-vibe

Keep in mind that with this approach, the vibe command is only available when the environment is activated.

Installation on Windows

Windows is supported, although Vibe is primarily designed for UNIX environments. Installation happens via PowerShell in two steps: the first command installs uv, and the second installs Vibe.

powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
uv tool install mistral-vibe

After installation, open a new terminal so the vibe command is recognized: the current PowerShell session retains the old PATH and would tell you the command doesn’t exist, even though it is installed.

Windows with WSL

If you use WSL (Windows Subsystem for Linux), simply follow the Mac/Linux instructions. This is actually the recommended method for an optimal experience on Windows, because the shell commands the agent executes are designed for a UNIX environment:

# In your WSL terminal
curl -LsSf https://mistral.ai/vibe/install.sh | bash

Verify the Installation

Regardless of the method used, always finish with a verification. This is the only way to know if the binary is truly accessible from your shell:

vibe --version

You should see the version number displayed (3.0.4 as of November 2, 2026; the 3.0 generation dates from October 19, 2026). If the command is not found, it’s almost never because the installation failed: it means the installation directory is not in your PATH.

Troubleshooting Common Issues

The vibe command is not found

After installation via uv, the binary is usually located in ~/.local/bin/. If this directory isn’t declared in your PATH, your shell can’t see it. Add it to your configuration file:

# In ~/.bashrc or ~/.zshrc
export PATH="$HOME/.local/bin:$PATH"

Then reload your shell so the change takes effect in the current session:

source ~/.bashrc
# or
source ~/.zshrc

Cache error with uv

Sometimes a previous installation leaves a corrupted cache, typically after a network interruption. The installation then fails with an error mentioning the cache. Rerun the command while bypassing it:

uv tool install mistral-vibe --no-cache

Python version conflict

On a machine where multiple interpreters coexist—a system Python 3.11 and a manually installed 3.12, for example—uv might select the wrong one. Explicitly force the target version:

uv tool install mistral-vibe --python python3.12

These three situations cover nearly all stuck installations. Make it a habit to rerun vibe --version after each fix.

Key Takeaways

  • Python 3.12+ is the only technical prerequisite
  • On Mac/Linux, the curl script is the fastest method
  • uv tool install is the recommended method to avoid conflicts
  • On Windows, prefer WSL for a better experience
  • Verify the installation with vibe --version