What agents can do explains what each runtime can reach. When an agent asks, the request appears as an approval card; Approvals covers the cards.
Before you begin
- Open the agent’s page: click its Boo in the sidebar, or right-click it on the Org chart and choose Open agent (see Agents).
- In the Details card, choose Permissions. It appears only for Clawboo Native and OpenClaw agents.
Let a Clawboo Native agent ask to run commands
1
Open the setting
On the agent’s page, choose Details > Permissions. You see Running commands.
2
Turn it on
Switch on Let this Boo ask to run commands.
3
Confirm
In the dialog Let this Boo ask to run commands?, press Allow it to ask.You should see Saved, and a note under the switch saying that commands run in the agent’s working folder, as you, with access to the network.
- Every command asks first. Nothing is remembered and there is no Always, so a command you allowed asks again the next time.
- Only runs with a working folder can ask. Team chat works in the team’s folder. A run on a task, such as a task handed out in team chat, one you start from the Board or one a routine made in the dashboard files, works in the task’s own folder inside it. A run inside a git repository, which you set up through the API, works in its worktree. One-to-one chat on the agent’s page works in the team’s folder too, and its requests wait above the message box.
- Never on Windows. The switch is there, but Clawboo does not offer the agent a way to run commands.
- One program at a time. A command is a program and its arguments, run without a shell, so pipes and redirects do not work. Programs that run other commands, such as shells,
python,nodeandnpx, are refused before you are asked; What agents can do lists them. - At most 10 commands per run. Each card waits 10 minutes, and the run waits with it.
- A refusal ends the asking. After you choose Don’t allow, or a card runs out of time, the agent cannot ask about another command for the rest of that run.
- The approved program runs, or nothing does. If the program changes on disk while the card waits, Clawboo does not run it.
Choose when an OpenClaw agent asks
On the agent’s page, Details > Permissions shows Execution Permissions with a Command Execution dropdown. The line under the dropdown describes the option you picked.
Pick an option and you should see Execution permissions updated. The agent follows it from its next message.
- The starting point. An agent you create in Clawboo starts on Ask for Unknown. For an agent created in OpenClaw itself, the dropdown shows Run Freely until you pick an option, because Clawboo has no setting stored for it.
- Clawboo applies the change at the OpenClaw Gateway. If the Gateway refuses it, for example while Clawboo is not connected to it, a message starting Not applied. appears and the dropdown goes back. Clawboo still keeps your choice in its own record, so after a reload the dropdown can show an option the Gateway is not using. Pick it again once the Gateway is connected.
- Changing the option keeps the list. Commands the agent may run without asking stay on file whichever option you pick. To remove one, revoke it (below).
- A separate default. The Command Approval card under Settings > System holds a default in OpenClaw’s own config; see System.
See what an OpenClaw agent may run without asking
Below the dropdown, Commands this Boo can run without asking lists the agent’s standing permissions. Each one comes from an Always you gave on a command card, or from OpenClaw’s own settings. A row names the program and says how wide the permission is:
A few rows carry more:
- and its companion rule: one Always wrote two rules, and Clawboo shows them as one permission. It groups them only when the agent has exactly one of each; otherwise the companion shows as its own row with Not removable here.
- On the narrowest kind: “clawboo cannot show which command: OpenClaw keeps only a fingerprint of it and the folder it ran in. The same command typed differently, or run elsewhere, asks again.”
- “Also granted to every Boo. Removing it here would not stop it.” Its revoke button is turned off.
Revoke a permission
1
Pick the row
Click the trash icon on the permission’s row.
2
Confirm
The dialog Revoke this standing permission? says the command will need your approval again the next time this agent runs it. For a grouped row, both rules go together. A command already approved and waiting to run may fail, because OpenClaw checks the whole rule set again before it starts. Press Revoke.
3
Check the result
You should see Standing permission revoked, and the row is gone. Clawboo reads the list again before it reports, so a row that is still there is still in force.
When the list says No standing permissions
The empty list comes in two versions, and they mean different things:
Treat the second version with care. It is also what you see when the OpenClaw Gateway runs on another computer, or keeps its data in a folder Clawboo is not reading. In both cases the agent can have permissions this list cannot show.
A red alert is different again. It starts clawboo could not read this computer’s permission list and ends “Nothing here is safe to trust until it can be read again.” Clawboo found the permissions but could not read them, or its server did not answer. The permissions on file still apply. Press Refresh; if the alert stays, check the permissions in OpenClaw itself.
Where Clawboo reads the list
Where Clawboo reads the list
Clawboo opens
state/openclaw.sqlite inside OpenClaw’s state folder, read-only. The folder is the first of:OPENCLAW_STATE_DIR,MOLTBOT_STATE_DIRorCLAWDBOT_STATE_DIR, when set in the environment Clawboo starts in~/.openclaw, when it exists~/.clawdbotor~/.moltbot, when one of them exists
OPENCLAW_STATE_DIR for Clawboo too. See Data and state for the other files Clawboo reads in OpenClaw’s folder.Limits
- Same computer only. The list reads OpenClaw’s files directly, so it works only when the Gateway runs on the same computer as Clawboo.
- This agent only. Permissions that apply to every agent show only as the footer count, and you change them in OpenClaw.
- Revoke only. You cannot create, edit or narrow a permission here. Always on a command card is how Clawboo adds one.
- No live updates. A permission you add by answering Always appears after you press Refresh.
Troubleshooting
The switch is on, but my Clawboo Native agent never asks
The switch is on, but my Clawboo Native agent never asks
The agent can ask only on a run with a working folder, and never on Windows. Team chat and one-to-one chat work in the team’s folder, and Board tasks and routines made in the dashboard work in the task’s own folder inside it, so the agent can ask there. A run that started before you switched it on cannot ask; send the next message, or start the task again.
Not applied. saved in clawboo, but the Gateway did not accept it
Not applied. saved in clawboo, but the Gateway did not accept it
The Gateway refused the new Command Execution option, or Clawboo is not connected to it. The agent keeps its old setting. Check OpenClaw under Settings > Workspace > Runtimes, then pick the option again.
the Gateway accepted the change and still lists those grants
the Gateway accepted the change and still lists those grants
Clawboo sent the revoke, and the Gateway’s reply still contains the permission. Press Refresh. If the row is still there, the permission is still in force; try the revoke again.
that grant is set for every Boo, not just this one, so it cannot be removed here
that grant is set for every Boo, not just this one, so it cannot be removed here
The permission is in the set that applies to every agent, so removing it from this agent would not stop it. Change it in OpenClaw.
those grants were already gone
those grants were already gone
Someone or something removed the permission before your revoke landed. Press Refresh to see the current list.
Under the hood
Under the hood
- Clawboo Native.
GETandPOST /api/agents/:agentId/shell(body{ "enabled": true }) read and set the switch, stored astools.shellin the agent’s config. A missing value means off, and the route answers 400 for other runtimes. The tool exists only on runs with a working folder, never on Windows, and a run can ask at most 10 times. - OpenClaw setting.
POST /api/exec-settingssaves Clawboo’s record, then writes the agent’s entry in the Gateway’s approvals policy under OpenClaw’s own agent id, with the valuesoff,on-missandalways. A refusal answers 502 withsavedLocally: true. Run Freely removes the agent’s ask setting but keeps its list. - The list.
GET /api/exec-allowlist?agentId=<id>answersokorabsent(200),not-applicablefor other runtimes, orunreadable(502, with the last known rule count). - Revoke.
POST /api/exec-allowlist/revokewith{ "agentId": "<id>", "keys": [...] }. Clawboo rewrites OpenClaw’s whole permissions document and checks the Gateway’s reply before it answers: 200revoked; 409already-absent,blocked-wildcardorno-such-agent; 502not-verified.
Next steps
- Approvals: answer the cards these settings raise.
- What agents can do: what each runtime can reach, with and without asking.
- Agents: the agent page and its Details card.
- OpenClaw: set up and manage the OpenClaw Gateway.
- System: the default Command Approval for OpenClaw agents.