How to Enable YOLO Mode in fount
fount has no YOLO mode, and no documented way to auto-approve anything. It is a character and chat platform, and coding editors reach it through its ideIntegration ACP bridge. That bridge asks for permission in only two places, and neither of them is offered when fount runs behind AgentRQ, so there is nothing for a YOLO switch to approve.
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 fount source (steve02081504/fount, commit 701259b) and the AgentRQ ACP Gateway source on October 30, 2026.
Does fount Have a YOLO Mode?
No. We found no flag, setting or session mode that turns approvals off, and fount's ACP bridge advertises no session modes of its own unless a character's interface supplies them.
What fount does have is a small set of editor tools. When the ACP client says it can, fount gives the character three tags: read a file through the editor, write a file through the editor, and run a command in the editor's terminal. Before a write or a terminal command, fount sends session/request_permission with two answers, Allow and Reject. Reads never ask. MCP servers passed in by the client are wired up as plugins and do not ask.
How fount Connects Over ACP
fount runs as a server, and editors talk to it through a small Deno script that forwards stdio to fount's ACP WebSocket. fount's IDE integration page gives you the exact command with your API key and character filled in. It looks like this:
How to Enable YOLO Mode in fount Through AgentRQ
For most agents, AgentRQ adds a per-task YOLO switch even when the agent has none. That only works when the agent asks for permission over ACP, and fount behind AgentRQ does not.
Connect fount to AgentRQ
Wrap fount's ACP command with the ACP Gateway (fount setup guide):
Use the deno run ... command above as <fount-acp-command>.
Why the YOLO Toggle Changes Nothing for fount
fount only offers its write and terminal tools when the ACP client says it supports file writes and terminals. The AgentRQ gateway does not advertise either, so fount's character gets no write or terminal tool, and fount never sends a permission request. The task's YOLO toggle and the workspace's YOLO Mode (Execute All) switch approve permission requests, so with none arriving they have nothing to do. Any tool calls that do happen, such as MCP tools, run without asking either way.
What AgentRQ Still Gives You With fount
- → A task to work from. Each task you assign starts a fount session, and you can reply to it from the web, your phone or Slack.
- → A record. The tool call history shows the tool calls fount reports.
- → Unattended runs. Scheduled tasks, event triggers and workflow steps can hand work to fount on their own.
A Safe Setup for fount
- → Restrict at the source. Since nothing asks, decide what a character can do through the MCP servers and plugins you give it, not through approvals.
- → Keep the API key private. The connection command carries your fount API key in the URL. Don't commit it.
- → Commit first. Start from a clean git tree if the character works on a repository, so any change is one
git resetaway.
FAQ
Does fount have a YOLO mode? No. fount has no flag, setting or session mode that auto-approves actions.
When does fount ask for permission? Before writing a file through the editor or running a command in the editor's terminal, and only when the ACP client supports those features. Reads and MCP tools do not ask.
Does AgentRQ's YOLO toggle work with fount? It has no effect. The AgentRQ gateway does not offer fount file writes or a terminal, so fount never sends a permission request for the toggle to approve.
How do I connect fount to AgentRQ? Run npx @agentrq/acp-gateway@latest -- followed by the deno run command from fount's IDE integration page.
For every other agent, see what YOLO mode is and how to turn it on in every coding agent.