██████████████████░░
██████████████████░░
████ ██████ ████░░
████ ██ ████░░
████ ████░░
████ ██ ██ ████░░
██ ██ ██░░
██████████████████░░
██████████████████░░
Mistral's open-source CLI coding assistant.
Mistral Vibe is a command-line coding assistant powered by Mistral's models. It provides a conversational interface to your codebase, allowing you to use natural language to explore, modify, and interact with your projects through a powerful set of tools.
[!WARNING] Mistral Vibe works on Windows, but we officially support and target UNIX environments.
Linux and macOS
curl -LsSf https://mistral.ai/vibe/install.sh | bash
Windows
First, install uv
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
Then, use uv command below.
uv tool install mistral-vibe
pip install mistral-vibe
read, write_file, edit).bash).grep (with ripgrep support).todo list to track the agent's work.ask_user_question).task)./) and file paths (@).@ mentions — .png, .jpg, .jpeg, .gif, .webp files are sent to vision-capable models (e.g. Mistral Medium 3.5) as native multimodal content.config.toml file.Vibe comes with several built-in agent profiles, each designed for different use cases:
default: Standard agent that requires approval for tool executions. Best for general use.plan: Read-only agent for exploration and planning. Auto-approves safe tools like grep and read.accept-edits: Auto-approves file edits only (write_file, edit). Useful for code refactoring.auto-approve: Auto-approves all tool executions. Use with caution.Use the --agent flag to select a different agent:
vibe --agent plan
To change the default agent used when --agent is not passed, set
default_agent in your config.toml:
default_agent = "plan"
Valid values are default, plan, accept-edits, auto-approve,
lean (only when listed in installed_agents), or the name of any
custom agent file in ~/.vibe/agents/ or the project's .vibe/agents/
directory. Subagents such as explore are not accepted.
Note:
default_agentapplies in both interactive and programmatic (-p/--prompt) sessions. Pass--auto-approveor--yolowith any agent when a run should approve all tool calls without prompting.
Vibe supports subagents for delegating tasks. Subagents run independently and can perform specialized work without user interaction, preventing the context from being overloaded.
The task tool allows the agent to delegate work to subagents:
> Can you explore the codebase structure while I work on something else?
🤖 I'll use the task tool to delegate this to the explore subagent.
> task(task="Analyze the project structure and architecture", agent="explore")
Create custom subagents by adding agent_type = "subagent" to your agent configuration. Vibe comes with a built-in subagent called explore, a read-only subagent for codebase exploration used internally for delegation.
The ask_user_question tool allows the agent to ask you clarifying questions during its work. This enables more interactive and collaborative workflows.
> Can you help me refactor this function?
🤖 I need to understand your requirements better before proceeding.
> ask_user_question(questions=[{
"question": "What's the main goal of this refactoring?",
"options": [
{"label": "Performance", "description": "Make it run faster"},
{"label": "Readability", "description": "Make it easier to understand"},
{"label": "Maintainability", "description": "Make it easier to modify"}
]
}])
The agent can ask multiple questions at once, displayed as tabs. Each question supports 2-4 options plus an automatic "Other" option for free text responses.
Vibe's interactive interface requires a modern terminal emulator. Recommended terminal emulators include:
Most modern terminals should work, but older or minimal terminal emulators may have display issues.
bash
cd /path/to/your/project
bash
vibe
~/.vibe/config.toml~/.vibe/.env for future useAlternatively, you can configure your API key separately using vibe --setup.
```
Can you find all instances of the word "TODO" in the project?
🤖 The user wants to find all instances of "TODO". The grep tool is perfect for this. I will use it to search the current directory.
grep(pattern="TODO", path=".")
... (grep tool output) ...
🤖 I found the following "TODO" comments in your project. ```
Simply run vibe to enter the interactive chat loop.
Ctrl+J or Shift+Enter for select terminals to insert a newline.@ symbol for smart autocompletion (e.g., > Read the file @src/agent.py).! to execute it directly in your shell, bypassing the agent (e.g., > !ls -l).Ctrl+G to edit your current input in an external editor.Ctrl+O to toggle the tool output view.Ctrl+T to toggle the todo list view.Ctrl+\ to toggle the debug console.Shift+Tab to cycle through agents (default, plan, ...)./exit, exit, quit, :q, or :quit in the input box, or press Ctrl+C / Ctrl+D twice within ~1 second. Set ask_confirmation_on_exit = false (or toggle it in /config) to make Ctrl+D quit on the first press; Ctrl+C always requires confirmation.You can start Vibe with a prompt using the following command:
vibe "Refactor the main function in cli/main.py to be more modular."
Vibe includes a trust folder system to ensure you only run the agent in directories you trust. When you first run Vibe in a new directory which contains a .vibe subfolder, it may ask you to confirm whether you trust the folder.
Trusted folders are remembered for future sessions. You can manage trusted folders through its configuration file ~/.vibe/trusted_folders.toml.
This safety feature helps prevent accidental execution in sensitive directories.
You can run Vibe non-interactively by piping input or using the --prompt flag. This is useful for scripting.
vibe --prompt "Refactor the main function in cli/main.py to be more modular."
By default, it uses your configured default_agent (default unless changed).
To approve all tool calls without prompting, pass --auto-approve or --yolo
(also available for interactive sessions):
vibe --prompt "Refactor the main function in cli/main.py to be more modular." --auto-approve
When using --prompt, you can specify additional options:
--max-turns N: Limit the maximum number of assistant turns. The session will stop after N turns.--max-price DOLLARS: Set a maximum cost limit in dollars. The session will be interrupted if the cost exceeds this limit.--max-tokens N: Set a maximum cumulative LLM token budget for the session, counting both prompt and completion tokens. The session will be interrupted if usage exceeds this limit.--agent NAME: Select the agent profile for this run.--auto-approve, --yolo: Approves all tool calls without prompting, including in interactive sessions. Can be combined with any --agent value.--enabled-tools TOOL: Enable specific tools. In programmatic mode, this disables all other tools. Can be specified multiple times. Supports exact names, glob patterns (e.g., bash*), or regex with re: prefix (e.g., re:^serena_.*$).--output FORMAT: Set the output format. Options:text (default): Human-readable text outputjson: All messages as JSON at the endstreaming: Newline-delimited JSON per messageExample:
vibe --prompt "Analyze the codebase" --max-turns 5 --max-price 1.0 --max-tokens 50000 --output json
[!WARNING] Voice mode is experimental and may change in future releases.
Voice mode allows you to dictate input using your microphone instead of typing.
Toggle voice mode on or off with the /voice slash command:
> /voice
| Shortcut | Action |
|---|---|
Ctrl+R |
Start recording |
| Any key | Stop recording |
Escape |
Cancel recording |
Ctrl+C |
Cancel recording |
Use slash commands for meta-actions and configuration changes during a session.
Vibe provides several built-in slash commands. Use slash commands by typing them in the input box:
> /help
You can define your own slash commands through the skills system. Skills are reusable components that extend Vibe's functionality.
To create a custom slash command:
SKILL.md fileuser-invocable = true in the skill metadataExample skill metadata:
---
name: my-skill
description: My custom skill with slash commands
user-invocable: true
---
Custom slash commands appear in the autocompletion menu alongside built-in commands.
Vibe's skills system allows you to extend functionality through reusable components. Skills can add new tools, slash commands, and specialized behaviors.
Vibe follows the Agent Skills specification for skill format and structure.
Skills are defined in directories with a SKILL.md file containing metadata in YAML frontmatter. For example, ~/.vibe/skills/code-review/SKILL.md:
name: code-review description: Perform automated code reviews license: MIT compatibility: Python 3.12+ user-invocable: true allowed-tools: - read -
$ claude mcp add mistral-vibe \
-- python -m otcore.mcp_server <graph>