Human-in-the-Loop Task Manager for AI Agents
Checked October 30, 2026 | All YOLO Mode guides

How to Enable YOLO Mode in Raxol

Raxol has no YOLO switch you can turn on. Its coding agent asks before every write, edit and shell command, in the terminal and over ACP alike. You can still get a YOLO mode, per task, by connecting it to AgentRQ.

This page is one of our YOLO mode guides, and part of our guide to YOLO mode in every coding agent. Everything below was checked against the Raxol source (DROOdotFOO/raxol, version 2.7.0) 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

Does Raxol Have a YOLO Mode?

Not one you can turn on. Raxol's agent harness has an internal option that turns its approval gate off, which its code comments call --yolo, but we found no command-line flag or setting that exposes it. raxol acp takes only --backend, --model and --help.

What Raxol does have:

  • → Approval prompts in the terminal app. In raxol code, press a to allow once, s to allow always for the session, or d to deny. Esc denies too.
  • → Plan mode. Shift+Tab or Ctrl+P turns it on. Raxol then refuses every mutating tool and only reads and plans.
  • → A working-directory fence. File tools resolve every path inside the working directory, symlinks included, and reject anything outside it. Shell commands are not sandboxed by default.

Reads such as read_file, grep and glob never ask. write_file, edit_file and bash always do.

How to Enable YOLO Mode in Raxol Through AgentRQ

Raxol always asks, so AgentRQ is where its YOLO switch lives: on for the tasks you choose, off for the rest.

Approve From the AgentRQ Task Instead of the Terminal

Connect Raxol to an AgentRQ workspace through the ACP Gateway (Raxol setup guide):

bash 
npx @agentrq/acp-gateway@latest -- raxol acp

Over ACP, Raxol sends a permission request for every write, edit and shell call, offering allow once and reject once. It fails closed: a refusal, an error or a disconnect all count as a deny, and reads keep working. Each 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 Raxol carries on.

Raxol waits 10 minutes for an answer, then treats the silence as a deny. That is shorter than the gateway's 30-minute limit, so for Raxol, --permission-timeout cannot give you more time to answer.

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. Every permission request in it is approved automatically and Raxol never waits, while every other task in the workspace still asks. Scheduled tasks, event triggers and workflow steps have the same switch, so an unattended job can run in YOLO while your interactive work stays supervised.

This is how Raxol gets a YOLO mode at all: Raxol keeps asking, and AgentRQ answers yes for that task, before Raxol's 10-minute limit runs out.

The YOLO toggle on a task in AgentRQ being switched on, then off again

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

A Safe YOLO Setup for Raxol

  • → 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.
  • → Bring your own sandbox. Raxol's file tools stay in the working directory, but bash does not. 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 lists every call the task made, including the ones that were auto-approved.

FAQ

Does Raxol have a YOLO mode? No user-facing one. Its harness can turn the approval gate off internally, but no flag or setting exposes that. Raxol asks before every write, edit and shell call.

How do I auto-approve Raxol's tool calls? Connect raxol acp to AgentRQ and turn on YOLO for the task. AgentRQ answers each request with allow.

What happens if nobody answers Raxol? After 10 minutes Raxol treats the request as denied, and the write or command does not run.

Does Raxol have a sandbox? Its file tools are confined to the working directory. Shell commands are not sandboxed by default, so use a container.

What is plan mode in Raxol? A mode, toggled with Shift+Tab or Ctrl+P in raxol code, where Raxol refuses every mutating tool and only reads and plans.

For every other agent, see what YOLO mode is and how to turn it on in every coding agent.

Start Free