---
title: "How to Enable YOLO Mode in Qoder CLI | AgentRQ Guidelines"
url: https://agentrq.com/guidelines/yolo-mode/qoder-cli
description: "Qoder CLI YOLO mode: qoder --yolo (bypass_permissions), Ctrl+Y in a session, or defaultPermissionMode in settings. What still asks, and safe use."
---

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

# How to Enable YOLO Mode in Qoder CLI

To run Qoder CLI in YOLO mode, start it with `qoder --yolo`, or press **Ctrl+Y** in a running session. YOLO is Qoder's name for the `bypass_permissions` permission mode, and one kind of `rm` still asks even then.

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 Qoder CLI docs at docs.qoder.com and the @qoder-ai/qodercli 1.1.81 npm package 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 Qoder CLI

YOLO skips approval prompts for file edits, shell commands, web fetches, MCP tools and subagents. A few path checks stay on: an `rm` that would remove the working directory or one of its parents, your home directory, the filesystem root or a top-level directory still asks, and that prompt has no "always allow". In headless mode, where nobody can answer, that `rm` is denied.

Non-default modes only take effect in trusted directories. In a folder you have not trusted, Qoder falls back to `default`.

## How to Enable YOLO Mode in Qoder CLI

| Where | How |
| --- | --- |
| Command line | `qoder --yolo`, `qoder --dangerously-skip-permissions` or `qoder --permission-mode yolo` |
| In a session | **Ctrl+Y**, or **Shift+Tab** to cycle modes |
| settings.json | `"general": { "defaultPermissionMode": "bypass_permissions" }` |

bash

```bash
qoder --yolo
```

All three flags mean `--permission-mode bypass_permissions`. Mode names are case-insensitive, and `bypassPermissions` and `yolo` are accepted too. Settings go in `~/.qoder/settings.json`, or in a project's `.qoder/settings.json` or `.qoder/settings.local.json`.

Organization admins can turn YOLO off for everyone with `"security": { "disableYoloMode": true }`. Then `--yolo` and Ctrl+Y stop working, and Shift+Tab skips the mode.

### The Halfway Options

| Mode | What it does |
| --- | --- |
| `default` | Safe reads run, sensitive actions ask |
| `accept_edits` | Approves safe file edits in the working directories, commands still ask |
| `auto` | A classifier decides, guided by your `autoMode` allow and soft_deny rules |
| `dont_ask` | Never prompts: anything that would ask is denied |

You can also write `permissions.allow`, `ask` and `deny` rules in settings, add one in a session with `/allow Bash(npm test)`, or pass `--allowed-tools 'Read,Bash(git status)'` for one run. **Allow for this session** at a prompt lasts until Qoder exits.

### Sandbox

Qoder CLI's permission docs describe no sandbox for the CLI, so YOLO in Qoder CLI runs with your own user's access.

## How to Enable YOLO Mode in Qoder CLI Through AgentRQ

Qoder CLI's own 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 Qoder CLI to an AgentRQ workspace through the [ACP Gateway](https://agentrq.com/docs/connect-acp-agent) ([Qoder CLI setup guide](https://agentrq.com/docs/agents/qoder-cli)):

bash

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

Then start the bridge with the same command minus `--login`. Qoder's docs say that in ACP mode, a call that would ask sends a permission request to the client, so the AgentRQ task becomes where you answer. Over ACP, Qoder offers its permission modes as session modes: **Default**, **Accept Edits**, **Auto**, **Don't Ask** and **Bypass Permissions**. Keep it in **Default** and leave `defaultPermissionMode` unset: in Bypass Permissions or Auto, Qoder decides on its own, and in Don't Ask it denies instead of asking, so either way nothing reaches AgentRQ. 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 Qoder CLI 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 Qoder CLI 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 Qoder CLI

- → **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.
- → **Leave the workspace-wide switch off.** Workspace settings also has **YOLO Mode (Execute All)**. Turn YOLO on per task instead, so it never outlives the job you trusted.
- → **Keep deny rules for the dangerous ones.** Qoder checks `permissions.deny` before anything else, so a deny rule still blocks a call that AgentRQ's YOLO would approve.
- → **Bring your own sandbox.** Qoder CLI has none, so run YOLO tasks in a container or a throwaway clone.
- → **Commit first.** Start every YOLO task from a clean git tree, so any change is one `git reset` away.
- → **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 Qoder CLI?** Start it with `qoder --yolo`, or press Ctrl+Y in a running session.

**Is qoder --yolo the same as --dangerously-skip-permissions?** Yes. Both mean `--permission-mode bypass_permissions`.

**What still asks in Qoder CLI's YOLO mode?** An `rm` that would remove the working directory or a parent of it, your home directory, the root or a top-level directory.

**Why does --yolo not work in my folder?** Non-default permission modes only take effect in trusted directories. In an untrusted one, Qoder falls back to default.

**How do I approve Qoder CLI commands remotely?** Connect Qoder CLI to [AgentRQ](https://agentrq.com) through the ACP Gateway and keep it in Default mode. 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).