Fleet docs v0.2.0-rc.448

Action rules

The action ladder decides, for each kind of action, what an agent does before it acts (spec-agents §7.2). It lives in one file of your home, actions.json, which you push with fleet home push like CLAUDE.md and settings.json. An admin's fleet layer (--layer fleet) sets rules for every agent.

The four rules, and blocked

Rule In actions.json What the agent does
Act act (the default) Does it, reports after
Act if pre-approved preapproved Does it when the target matches a standing approval, else asks
Ask first ask Waits for your yes in the inbox
Hand off handoff Does not do it; tells you what to do
Blocked listed in blocked Never, for any agent, whatever its rule

The file

{
  "ladder":   {"spend-money": "ask", "push-default": "handoff"},
  "approved": {"spend-money": ["probe-*"]},
  "blocked":  ["delete-data"],
  "kinds":    {"cross-message": {"title": "Message another agent", "ops": ["send"]}}
}
  • ladder: kind to rule. A kind with no rule is act.
  • approved: standing approvals for preapproved kinds, as patterns of the target (*, ?).
  • blocked: kinds no agent may do. The layers join their lists, so your layer can block more than the fleet layer but never unblock what it blocked.
  • kinds: new kinds, or a new definition of a built-in one. A kind binds fleet operations (ops) and Claude Code permission rules (tools).

fleet home push refuses a file with an unknown key, rule or op. The layers merge per key (the later layer wins: fleet, then you, then a bot), except blocked.

Built-in kinds

Kind Fleet checks Tools a turn loses when the rule is not act
message-outside nothing none: add your channel's tools, such as mcp__slack__*
push-default nothing Bash(git push origin main:*), HEAD:main, and the same for master
deploy nothing Bash(kubectl apply:*), Bash(helm install:*), Bash(helm upgrade:*)
spend-money spawn (an agent starts a helper) none
delete-data nothing Bash(kubectl delete:*), Bash(dropdb:*)
change-config secret.rotate, workspace.new (a chat makes repos) none

The ops a kind can bind: spawn, send, board.post, workspace.new, secret.rotate.

What is enforced

  • Fleet operations (ops) are checked by the server when an agent asks for them. Your own calls are not on the ladder. Hand off and blocked are refused with what to do instead. Ask first, and pre-approved with no matching standing approval, post an approval to your inbox and refuse until you answer. The agent sleeps meanwhile (waiting for you, no process runs), and your answer starts its next turn. Approve it, and the agent's next try of the same action on the same target goes. Reject it, and the agent gets your reason.
  • Tools of every kind whose rule is not act are passed to Claude Code in --disallowedTools for each turn, so no setting in a repo turns them back on. A tool cannot wait for an approval, so ask first and pre-approved deny the tools too: you do the action, or change the rule. A permission rule matches the start of a command: git -C . push origin main is another command.
  • Everything else is a rule the agent reads. The rules that are not act are added to the agent's CLAUDE.md, each marked enforced or not. Only the enforced part is a boundary.

fleet home ls --layer effective lists the merged files your next turn gets, actions.json among them; GET /v1/home?layer=effective is the merged home itself, with the rules in its CLAUDE.md.