---
title: "How to Enable YOLO Mode in Kaagum | AgentRQ Guidelines"
url: https://agentrq.com/guidelines/yolo-mode/kaagum
description: "Kaagum has no YOLO mode: it asks before every tool call, and its tools run sandboxed. AgentRQ adds a per-task YOLO switch over ACP."
---

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

# How to Enable YOLO Mode in Kaagum

Kaagum has no YOLO mode. It is a small, security-focused agent written in Guile, and it asks before every tool call, with no flag or setting to skip that. You can still get YOLO for Kaagum through AgentRQ, one task at a time, because Kaagum sends every approval as an ACP permission request.

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 Kaagum source (git.systemreboot.net/kaagum, version 0.1.0, commit 3d286e6) 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)

## Does Kaagum Have a YOLO Mode?

No. Kaagum's command line takes a model, an API base URI, the commands that fetch its API keys and a trace file, and nothing that changes approvals. It has no session modes either. Every tool call starts out waiting for approval, and the client is offered four answers:

- → **Allow once** and **Reject once** decide this call.
- → **Allow always** and **Reject always** decide every later call to the same tool, for the rest of the session.

So the nearest thing to YOLO inside Kaagum is answering **Allow always** once per tool.

## What Kaagum's Tools Can Do

Kaagum's tool set is deliberately small, and all of it reads rather than writes:

| Tool | What it does |
| --- | --- |
| read, list, search | read a file, list files, grep for a pattern |
| forge issue reader | read an issue thread on GitHub or Forgejo |
| Kagi search and extract | web search and page extraction, when you give it a Kagi key |

There is no shell tool, and writing files is not implemented yet. Filesystem tools run in containers with no network access that can only see the working directory. Network tools can only reach specific hard-coded endpoints. Kaagum also never uses the ACP client's own file read and write.

That shapes what YOLO means here. Approving everything lets Kaagum read and search your project and the web without stopping. It cannot edit or run anything, whatever you approve.

## How to Enable YOLO Mode in Kaagum Through AgentRQ

Kaagum has no UI of its own, so it always runs behind an ACP client. With AgentRQ as that client, its permission requests reach you on the web, your phone or Slack, and a task can be switched to YOLO.

### Approve From the AgentRQ Task Instead of the Terminal

Kaagum speaks ACP on stdio as soon as it starts, so the command the [ACP Gateway](https://agentrq.com/docs/connect-acp-agent) wraps is plain `kaagum` with its options ([Kaagum setup guide](https://agentrq.com/docs/agents/kaagum)). For example, with an OpenRouter key kept in `pass`:

bash

```bash
npx @agentrq/acp-gateway@latest -- kaagum --api-key-command="pass openrouter.ai" --model=anthropic/claude-sonnet-4.6
```

`--api-key-command` is required. It names the command Kaagum runs to fetch the key, so the key itself never sits in your shell history.

Each tool call now shows up in the AgentRQ task as a permission request. Answer **Allow Once**, **Always Allow** or **Deny** from wherever you are, and Kaagum 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 Kaagum 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 Kaagum

- → **YOLO is low-risk here, but not free.** Kaagum's tools only read, and they are sandboxed, so the main costs of YOLO are tokens and Kagi queries. Set limits with your model provider.
- → **Start Kaagum in the right directory.** Its filesystem tools see only the working directory, so start the gateway from the project you mean it to read.
- → **Leave the workspace-wide switch off.** Turn YOLO on per task instead, so it never outlives the job you trusted.
- → **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 Kaagum have a YOLO mode?** No. It asks before every tool call and has no flag, setting or session mode that skips approval.

**How do I stop Kaagum asking about the same tool?** Answer **Allow always**. Kaagum then approves that tool for the rest of the session.

**Can Kaagum edit files or run commands?** Not in version 0.1.0. Its tools read files, list and search them, read forge issues and search the web.

**Does Kaagum have a sandbox?** Yes. Filesystem tools run in containers with no network that see only the working directory, and network tools reach fixed endpoints only.

**How do I get YOLO mode in Kaagum?** Connect it to [AgentRQ](https://agentrq.com) through the ACP Gateway and turn on the YOLO toggle for a task. Every permission request in that task is then approved automatically.

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).