---
title: "How to Enable YOLO Mode in DimCode | AgentRQ Guidelines"
url: https://agentrq.com/guidelines/yolo-mode/dimcode
description: "DimCode's YOLO mode is Full access: pick it with /approvals in the terminal UI, or the Full Access permission over ACP. Plus the Approve for me option."
---

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

# How to Enable YOLO Mode in DimCode

DimCode, the coding agent from ArcShips, calls its YOLO mode **Full access**. In the terminal UI, type `/approvals` and choose **Full access**, then confirm the warning. DimCode has no command-line flag for it. Over ACP the same setting is the session's **Permission** option, set to **Full Access**.

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). DimCode's source is closed and its docs are short, so everything below was checked against its README and the released binary (npm dimcode 0.5.22, the version 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](https://agentrq.com/assets/sketches/yolo-mode.svg)

## What YOLO Mode Turns Off in DimCode

`/approvals` opens the **Tool Approvals** dialog with three choices:

| Choice | What it does |
| --- | --- |
| Default permissions | Read tools run automatically, write tools ask |
| Approve for me | DimCode reviews each command itself: routine actions pass, unsafe ones ask you |
| Full access | All tools run automatically, permissions are bypassed |

Choosing Full access asks you to confirm, with a warning that it "reduces confirmation prompts" and can run sensitive actions, file changes or external commands directly. We found no sandbox in DimCode, so in Full access those commands run on your machine with your rights.

## How to Enable YOLO Mode in DimCode

text

```text
/approvals
```

Pick **Full access**, then confirm. At a normal prompt you answer each request with `Y` or `N`. `Tab` switches between agent mode and plan mode, which is separate from the approval setting.

Over ACP, DimCode reports a **Permission** option that clients can show as a dropdown:

| Permission | Effect |
| --- | --- |
| Read Only | Read-only file tools. Writes, network and process execution are denied |
| Workspace Write | Reads and writes in the workspace and git commands run. Other commands and network access ask |
| Full Access | All tools, no approval prompts |

### The Halfway Option

**Approve for me** is DimCode's middle ground in the terminal UI. Instead of you, the agent judges each command, lets routine ones through and stops to ask about the unsafe ones. Over ACP, **Workspace Write** plays a similar role with fixed rules: edits and git run, everything else asks.

## How to Enable YOLO Mode in DimCode Through AgentRQ

DimCode's Full access lasts for a 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 DimCode to an AgentRQ workspace through the [ACP Gateway](https://agentrq.com/docs/connect-acp-agent) ([DimCode setup guide](https://agentrq.com/docs/agents/dimcode)):

bash

```bash
npx @agentrq/acp-gateway@latest --agent dimcode
```

Keep the session's Permission off Full Access. DimCode sends its approvals to the ACP client as permission requests, and its default permissions let read tools run and ask before writes, edits and commands. 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 DimCode 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 DimCode 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 DimCode

- → **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.** Turn YOLO on per task instead, so it never outlives the job you trusted.
- → **Bring your own sandbox.** DimCode 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

**Does DimCode have a YOLO mode?** Yes. It is called Full access. Type `/approvals` in the terminal UI and choose it.

**Is there a command-line flag for YOLO in DimCode?** No. Full access is set with `/approvals`, or with the Permission option over ACP.

**What is Approve for me in DimCode?** A middle setting where DimCode reviews each command itself. Routine actions run, and unsafe ones still ask you.

**Does DimCode have a sandbox?** We found none. Run Full access sessions in a container or a throwaway clone.

**How do I approve DimCode actions remotely?** Connect DimCode 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).