How to Enable YOLO Mode in Corust Agent

Corust Agent, the Rust-focused coding agent from Corust AI, has no command line of its own. It runs inside an ACP client such as Zed, and its YOLO mode is one of three session modes the client shows: default, readonly and yolo. Pick yolo in your client's mode selector and Corust stops asking.

This page is one of our YOLO mode guides, and part of our guide to YOLO mode in every coding agent. Corust publishes no source and no permission docs, so everything below was read from the release binary (Corust-ai/corust-agent-release, version 0.6.0, the one in the ACP registry) 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

What YOLO Mode Turns Off in Corust Agent

Corust ships as one binary, corust-agent-acp, which speaks only ACP. Its three session modes come with these descriptions:

Mode	Description in the binary
`default`	"Current behavior: follow permission prompts and workspace rules."
`readonly`	Read-only: the agent cannot modify files
`yolo`	"Auto-allow every action that requires permission."

The binary also holds a third description, "Auto-reject every action that requires permission", which fits readonly. Any other mode id is refused with "Supported modes: default, readonly, yolo."

We found no sandbox in Corust. In yolo, its commands run on your machine with your user's rights.

How to Enable YOLO Mode in Corust Agent

Open a Corust session in your ACP client and switch the session mode to yolo. In Zed, that is the mode selector in the agent panel. Switch back to default to get the prompts again.

The Halfway Option

In default mode, Corust's prompts include an Always allow answer. That is the middle ground: it stops the prompts for that kind of action without turning on YOLO for everything. Corust keeps its command allow lists in a command-permissions.yaml file in its home folder, ~/.corust-agent unless CORUST_HOME says otherwise.

readonly is the other direction: useful when you want Corust to read and explain a Rust codebase without touching it.

How to Enable YOLO Mode in Corust Agent Through AgentRQ

Corust's yolo mode lasts for a session, and you have to be at the client to pick it. AgentRQ lets you make the decision per task, and answer from somewhere other than the editor.

Approve From the AgentRQ Task Instead of the Terminal

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

bash

npx @agentrq/acp-gateway@latest --agent corust-agent --allow-unverified-agent

Keep the session out of yolo. Corust sends each permission request to the ACP client, which is now AgentRQ. Each one 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 Corust 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 Corust 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.

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 Corust Agent

→ 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. cargo check and cargo test are good candidates. Prune that list in workspace settings now and then.
→ Leave the workspace-wide switch off. Turn YOLO on per task instead, so it never outlives the job you trusted.
→ Bring your own sandbox. Corust 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 lists every call the task made, including the ones that were auto-approved.

FAQ

Does Corust Agent have a YOLO mode? Yes. It is the yolo session mode, which auto-allows every action that would ask for permission.

How do I turn on YOLO mode in Corust Agent? Switch the session mode to yolo in your ACP client, such as the mode selector in Zed's agent panel. Corust has no command-line flag for it.

What modes does Corust Agent have? Three: default, which follows permission prompts and workspace rules, readonly, and yolo.

Does Corust Agent have a sandbox? We found none. Run YOLO sessions in a container or a throwaway clone.

How do I approve Corust Agent actions remotely? Connect Corust Agent 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.