Approve what your agents ask for
Agents stop and ask before risky steps. Allow or deny them, approve requests in the Inbox, and choose how often they ask.
Your agents stop and ask before a step that could change things you care about, like running a command or changing a Yardmaster setting. You decide each one, and you choose how often they ask.
There are two kinds of request. One appears inside a chat, when an agent wants to do something on your computer. The other appears in the Inbox, when an agent asks to change something in Yardmaster itself.
Answer a request inside a chat#
When an agent needs permission, its session shows Permission and moves to your Inbox. Open it: a card above the message box says what the agent wants to do and which tool is asking.
Read the card.
Click Allow to let it go ahead, or Deny to stop it.
To stop the questions for the rest of this chat, click the arrow next to Allow and choose Allow everything in this chat. It still asks before sensitive files, such as passwords, keys and logins. The arrow is there in Claude chats on your computer; chats started by email, and Yardmaster on your phone, show only Allow and Deny.
To skip every question, sensitive files too, choose Full Send there and confirm. Its red badge atop the chat turns it off.
When an agent proposes a plan first, the card offers Approve plan and Request changes instead. Request changes puts the cursor in the message box so you can say what to change.
Approve a request in the Inbox#
Requests to change Yardmaster itself (a setting, a tag, a scheduled job, an automation) wait in the Approvals group of your Inbox. Nothing happens until you answer.
Open the Inbox and click the request under Approvals.
Read what it would change.
Click Approve, or Reject to turn it down.
With an approval open, you can also press EnterEnterEnterEnter to approve and XXXX to reject. The keys do nothing while you are typing in a box, and holding one down counts as a single press.
Approve several at once#
When two or more requests wait in Approvals, the group's header shows Approve all, with the number of requests. Click it and confirm once. You can also select several rows, right-click one of them and choose Approve 2 selected (the number is how many you picked).
If any of them spend money or delete things, the confirm names each one and says so. Cancel is selected, so pressing EnterEnterEnterEnter does not approve the batch: click Approve all 3 in the confirm (the number is how many) to go ahead. Slack posts and a few other requests never join a bulk approval: open each one and approve it on its own.
Stop being asked about one kind of request#
On an approval, click the arrow next to Approve and pick where to always allow that kind of action: For this project (shown when the action belongs to a project), or Everywhere. It applies right away, approves the request in front of you as well, and shows a message with Undo for a few seconds. For actions that can spend money or delete things, Yardmaster asks you to confirm first.
Some requests have no arrow: those can never be always allowed, so Yardmaster asks every time.
It applies to that one kind of action only: always allowing a new tag never allows deleting one. To be asked again, remove it under Settings > CLI Control > Always-allowed actions.
Choose how often agents ask#
Agent Permission Level decides how much a Claude agent does on its own before it stops to ask you. You may have picked one when you first opened Yardmaster; change it any time:
Read-only: asks before writing any file or running any command.
Guarded (the default): edits files in the project on its own, and asks before commands, config files or anything outside the project.
Autonomous: edits and runs commands in the project on its own, and asks only before writing outside it.
Full trust: never asks, except about sensitive files.
If your agent keeps asking about every command, that is Guarded working as designed. Pick Autonomous to let it run commands inside the project.
To change one chat only, open its menu (the three dots above the conversation) and pick a level under Chat permissions. Other chats keep the level from Settings.
Two more switches sit next to it in Settings > Workflow. Auto-Approve Plans (off at first) approves an agent's plan for you, so you skip the Approve plan step. Auto-Approve Config File Writes (on at first) only matters at the Full and Autonomous levels, where it lets Claude change its own settings files, such as CLAUDE.md, without asking. At Guarded and Read-only, those changes always ask.
Full Send in detail. With Full Send on, the agent can read or change your passwords, SSH keys, cloud logins, your git login and the files your terminal runs at startup without asking, so turn it on only for a chat you are watching. Click Cancel in the warning to leave everything as it was.
When Full Send ends. It lasts for this chat only. It ends when you close or archive the chat and whenever Yardmaster restarts, and you can also turn it on or off under Chat permissions in the chat's menu. Background jobs, chats started by email and research chats waiting to leave research mode keep their own limits, and it can't be turned on from your phone.
Which agents this covers. Agent Permission Level and Chat permissions apply to Claude Code sessions. Other engines manage their own approvals: Codex has its own Codex permission level in Settings > Accounts.
Which Yardmaster changes need approval. Settings > CLI Control > Approval requirements lists each kind of change an agent can request, with a switch for whether it waits for you.
Who asked. An approval shows the session that requested it in a Generated by row (a settings change calls it Requested by). Click the name to open that session.
Learn Yardmaster, Many agents, one calm inbox: lesson 2 of 3
Answer an approval
Related
- Add and organize your projectsA project is a folder on your computer that your agents work in. Add one, group them, and change a project when its folder moves.
- Start and manage sessionsA session is one conversation with an agent, working in one project. Start one, read its status, and pause, snooze or archive it.
- Keep long sessions affordableEvery reply re-reads the whole conversation. Yardmaster warns you when a session gets large, holds costly automatic replies, and can continue in a fresh session.