---
title: "How to Enable YOLO Mode in Mistral Vibe | AgentRQ Guidelines"
url: https://agentrq.com/guidelines/yolo-mode/mistral-vibe
description: "Mistral Vibe YOLO mode: vibe --yolo (or --auto-approve), the auto-approve agent, Shift+Tab, default_agent in config.toml, and per-tool permissions."
---

![](https://agentrq.com/assets/agent-icons/mistral-vibe.png) Checked October 30, 2026 | [All YOLO Mode guides](https://agentrq.com/guidelines/yolo-mode/)

# How to Enable YOLO Mode in Mistral Vibe

To run Mistral Vibe in YOLO mode, start it with `vibe --yolo`, or its longer name `vibe --auto-approve`. Vibe also has an agent profile called **auto-approve** that does the same job, and you can switch to it with Shift+Tab in a running session.

This page is one of our [YOLO mode guides](https://agentrq.com/guidelines/yolo-mode/), and part of our guide to [YOLO mode in every coding agent](https://agentrq.com/blog/what-is-yolo-mode-and-how-to-turn-it-on-in-every-coding-agent). Everything below was checked against the Mistral Vibe source and README (mistralai/mistral-vibe, version 3.0.4, commit 338ad4b) on October 30, 2026.

![Animated sketch of YOLO mode in AgentRQ: claude waits to run go test, YOLO is flipped on for the task, and every later edit and test run lands auto-allowed in the Trajectory view](https://agentrq.com/assets/sketches/yolo-mode.svg)

## What YOLO Mode Turns Off in Mistral Vibe

Vibe decides what asks through **agent profiles**. The built-in ones are:

| Agent | What asks |
| --- | --- |
| `ask` | every tool call |
| `accept-edits` | everything except file edits. This is the default. |
| `auto-approve` | nothing |

A fourth one, `smart-approve`, uses a model to classify each call and only asks about risky ones. It is being rolled out gradually, so you may not see it yet.

YOLO approves every tool call. Vibe runs tools on your own machine, so there is no sandbox for YOLO to turn off. Its only sandbox is an experimental one for programmatic runs, where an outside server hosts the sandbox.

## How to Enable YOLO Mode in Mistral Vibe

| Where | YOLO | Halfway |
| --- | --- | --- |
| Command line | `vibe --yolo` or `--auto-approve` | `vibe --agent accept-edits` |
| Agent profile | `vibe --agent auto-approve` |  |
| In a session | Shift+Tab to auto-approve | Shift+Tab to accept-edits |
| config.toml | `default_agent = "auto-approve"` | `[tools.<name>] permission = "always"` |

bash

```bash
vibe --yolo
```

`--yolo` works with any `--agent` and in both interactive and programmatic runs. For a one-shot run:

bash

```bash
vibe --prompt "fix the failing tests" --auto-approve
```

**Shift+Tab** cycles through the agents, so it reaches `auto-approve` without a restart. To start every session in it, set the default in `~/.vibe/config.toml`:

toml

```toml
default_agent = "auto-approve"
```

Organizations can forbid all of this with `enable_auto_approve = false` in a managed config. The auto-approve agent and the `--yolo` flag are then ignored, and per-tool permissions still apply.

### The Halfway Option: Per-Tool Permissions

Each tool can be set to `always`, `ask` or `never` in `config.toml`, and the shell tool also takes allowlists and denylists. For example, to stop asking before reads:

toml

```toml
[tools.read]
permission = "always"
```

Calls that reach outside the working directory still ask by default. `outside_workdir = "deny"` refuses them instead.

## How to Enable YOLO Mode in Mistral Vibe Through AgentRQ

Mistral Vibe's own YOLO switch covers a whole session. AgentRQ lets you make the decision per task, and answer from somewhere other than the terminal.

### Approve From the AgentRQ Task Instead of the Terminal

Connect Mistral Vibe to an AgentRQ workspace through the [ACP Gateway](https://agentrq.com/docs/connect-acp-agent) ([Mistral Vibe setup guide](https://agentrq.com/docs/agents/mistral-vibe)). Log in once, then start the bridge:

bash

```bash
npx @agentrq/acp-gateway@latest --login --agent mistral-vibe
npx @agentrq/acp-gateway@latest --agent mistral-vibe
```

Vibe's ACP server offers its agents as session modes: `ask`, `accept-edits` and `auto-approve` (plus `smart-approve` where it is enabled). Whichever one a session starts in, AgentRQ switches it to `ask`, the mode that sends every call to you, and switches it back if it leaves.

Each permission request now shows up in the AgentRQ task on the web, on your phone or in Slack, together with the command or edit it is asking about. Answer **Allow Once**, **Always Allow** or **Deny** from wherever you are, and Mistral Vibe carries on. If nobody answers within 30 minutes, the gateway cancels the turn instead of guessing. Change the limit with `--permission-timeout`.

### Turn On YOLO for One Task

Flip the **YOLO** toggle on a task, or when you create it, to put just that task in [YOLO mode](https://agentrq.com/features/yolo-mode). Every permission request in it is approved automatically and Mistral Vibe never waits, while every other task in the workspace still asks. [Scheduled tasks](https://agentrq.com/features/task-scheduling), [event triggers](https://agentrq.com/features/events) and [workflow](https://agentrq.com/features/workflows) steps have the same switch, so an unattended job can run in YOLO while your interactive work stays supervised.

![The YOLO toggle on a task in AgentRQ being switched on, then off again](https://agentrq.com/assets/guidelines/yolo-mode-task-toggle.gif)

### Turn YOLO On or Off in Workspace Settings

To make YOLO the default for a whole workspace, open the workspace, go to **Settings**, choose the **Automations** tab and flip **YOLO Mode (Execute All)**. Click **Update Workspace** to save. Switch it off the same way. The switch is off by default, and every permission request in the workspace is approved automatically while it is on.

![Workspace Settings in AgentRQ: the YOLO Mode (Execute All) switch turned on and saved, then off and saved](https://agentrq.com/assets/guidelines/yolo-mode-workspace-settings.gif)

### A Safe YOLO Setup for Mistral Vibe

- → **Allow the boring tools, not everything.** **Always Allow** adds the tool to the workspace's auto-approved list, so the routine calls stop asking and the risky ones still do. Prune that list in workspace settings now and then.
- → **Keep tool permissions at ask.** A tool set to `always` in `config.toml` never reaches AgentRQ, whatever mode the session is in.
- → **Leave the workspace-wide switch off.** Turn YOLO on per task instead, so it never outlives the job you trusted.
- → **Bring your own sandbox.** Vibe runs tools on your machine, so run YOLO tasks in a container or a throwaway clone.
- → **Read the record.** The [tool call history](https://agentrq.com/features/tool-call-history) lists every call the task made, including the ones that were auto-approved.

## FAQ

**How do I enable YOLO mode in Mistral Vibe?** Start it with `vibe --yolo`, or `vibe --auto-approve`. They are the same flag.

**How do I switch Mistral Vibe to YOLO in a running session?** Press Shift+Tab until the auto-approve agent is selected.

**How do I make YOLO the default in Mistral Vibe?** Set `default_agent = "auto-approve"` in `~/.vibe/config.toml`.

**What is the accept-edits agent in Mistral Vibe?** The default agent. It approves file edits on its own and asks before other tool calls.

**Does Mistral Vibe have a sandbox?** Not for normal sessions. Tools run on your machine, so use a container for YOLO runs.

**How do I approve Mistral Vibe tool calls remotely?** Connect it to [AgentRQ](https://agentrq.com) through the ACP Gateway. Its permission requests show up in the task on the web, your phone or Slack.

For every other agent, see [what YOLO mode is and how to turn it on in every coding agent](https://agentrq.com/blog/what-is-yolo-mode-and-how-to-turn-it-on-in-every-coding-agent).