How to Enable YOLO Mode in Minion Code
To run Minion Code in YOLO mode, start it with mcode --dangerously-skip-permissions, or mcode acp --dangerously-skip-permissions for its ACP server. That starts the session in Bypass Permissions mode, which skips every prompt and also its dangerous-command checks. A gentler option, Don't Ask, skips the prompts but keeps those checks.
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 Minion Code source and README (femto/minion-code, version 0.1.45, commit 26e373e) on October 30, 2026.
Minion Code's Permission Modes
Minion Code has five session modes:
| Mode | Asks before | Dangerous-command checks |
|---|---|---|
| Default | every tool that can change something | on |
| Accept Edits | everything except file edits and the todo list | on |
| Plan Mode | nothing: read-only tools only | not needed |
| Don't Ask | nothing | on |
| Bypass Permissions | nothing | off |
Read-only tools never ask in any mode: reading, globbing, grepping and listing files, web search and fetch, and reading the todo list.
Bypass Permissions is the full YOLO mode. Don't Ask is YOLO with a seatbelt. Either way, the bash tool itself still refuses commands containing rm -rf, sudo, su, chmod 777, mkfs or dd if=. That list is built into the tool and no mode turns it off.
Minion Code has no sandbox. Commands run on your machine with your permissions.
How to Enable YOLO Mode in Minion Code
For the ACP server:
To make it the default for the ACP server, add skip_permissions to ~/.minion/minion-code.json, the same file mcode model writes to:
The Halfway Option
Accept Edits stops the prompts for file edits and keeps them for shell commands and other tools. At an ACP prompt, Always allow this tool stops Minion Code asking about that tool again. The README says the choice is saved under ~/.minion/sessions/.
How to Enable YOLO Mode in Minion Code Through AgentRQ
Minion Code'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 Minion Code to an AgentRQ workspace through the ACP Gateway (Minion Code setup guide). Log in once, then start the bridge:
Leave skip_permissions out of ~/.minion/minion-code.json, or the session starts in Bypass Permissions and nothing reaches AgentRQ. Of the five modes, only Default and Accept Edits send permission requests, so keep the session in Default to see everything.
Each permission request now shows up in the AgentRQ task on the web, on your phone or in Slack, together with the tool and its input. Answer Allow Once, Always Allow or Deny from wherever you are, and Minion Code 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. Every permission request in it is approved automatically and Minion Code 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. Unlike Bypass Permissions, this keeps Minion Code's dangerous-command checks on.
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.
A Safe YOLO Setup for Minion Code
- → Prefer AgentRQ YOLO to Bypass Permissions. It approves the same calls but leaves the dangerous-command checks in place.
- → 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.
- → Bring your own sandbox. Minion Code 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 resetaway. - → Read the record. The tool call history lists every call the task made, including the ones that were auto-approved.
FAQ
How do I enable YOLO mode in Minion Code? Start it with mcode --dangerously-skip-permissions. For the ACP server, use mcode acp --dangerously-skip-permissions.
What is the difference between Don't Ask and Bypass Permissions in Minion Code? Both skip permission prompts. Don't Ask keeps the dangerous-command checks, and Bypass Permissions turns them off.
Can Minion Code run rm -rf in YOLO mode? No. Its bash tool refuses commands containing rm -rf, sudo, su, chmod 777, mkfs or dd if= in every mode.
Does Minion Code have a sandbox? No. Commands run on your machine, so use a container or a throwaway clone for YOLO runs.
How do I approve Minion Code tool calls remotely? Connect mcode acp to AgentRQ 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.