This page gives the permission model of the actors of the orchestration. An actor is a session or a subagent that runs commands for the orchestration. The page has one table. The table says which kind of command each actor runs. The page also gives the place of the rules, the report chain and the facts of a measure.
The reader of this page is the orchestrator. It reads the table and the lists of the allowed commands. Each actor reads its own row when a step needs it.
- An actor is a session or a subagent that runs commands for the orchestration.
- A phase is plan, execute or review, as the task states give them.
- A kind of command is one of K1 to K16 in The kinds of command.
- The project file is
.claude/settings.jsonof the repo. - The user file is
$HOME/.claude/settings.json. - A user-level file is a file as Terms of the question-pane page defines it.
- A denial and a check failure are as the tool-block rule defines them.
A cell of the table has one of three values:
- "runs": the list of the actor for that kind holds a command that runs with no word of the user.
- "asks the user": each command of the list for that kind runs only after a word of the user for that call.
- "never runs": the actor has no list for that kind.
- K1: a read-only
taskercommand, as the orchestrator-command rule defines it. - K2: a task change, as the same rule defines it.
- K3: a
gitread. - K4: a
gitwrite. Agit fetchcounts here, because it changes the refs of the clone. - K5: a
ghread. - K6: a write of the text of an issue or a comment.
- K7: a write of the metadata of an issue.
- K8: a
herdrread. - K9: a
herdrcommand that acts on another pane. - K10: a message to another session.
- K11: the start of a subagent with the Agent tool.
- K12: a write of a file in the folder of the actor.
- K13: a write of a user-level file.
- K14: a write of a tracked file.
- K15: a read of a credential file or of a file under
$HOME/.claude/. - K16: a command that no kind names. For an actor that gets a list, the K16 cell follows its list "Named other commands" in the allowed commands, by the cell values of Terms. The sessions of tasker get no list, so their K16 cell follows The limits of each role.
Each cell of an orchestration actor follows its list in the allowed commands. This table copies
no list. The cells of the three sessions of tasker follow
The limits of each role,
The environment of the shell and
The limits of the roles. A call that the plan mode, a deny rule, the hook, the
sandbox or the missing GitHub token and ssh agent blocks says "never runs". Each other call says "runs". For K16, the
three sessions run the commands that these limits allow, for example the tests and the npm scripts of the execute
session in its worktree. These rows change no limit. The cells of the three session rows are for the kind claude-code.
The limits of the kinds codex and pi are in their own sections of assistants.md. The column "Where the rules live"
links to those sections, and this table does not repeat them. For pi, the rules that no seam enforces are docs only.
| Actor | K1 | K2 | K3 | K4 | K5 | K6 | K7 | K8 | K9 | K10 | K11 | K12 | K13 | K14 | K15 | K16 | Where the rules live | Gets the report of a denial |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| The orchestrator | runs | asks the user | runs | runs | runs | runs | runs | runs | runs | runs | runs | runs | never runs | never runs | never runs | runs | Docs only. List | The user, in its question pane |
| A task subagent for a whole ticket | runs | runs | runs | runs | runs | runs | never runs | never runs | never runs | never runs | never runs | runs | never runs | runs | never runs | runs | Docs only. List | The orchestrator |
| A task subagent for one task change | never runs | runs | never runs | never runs | never runs | never runs | never runs | never runs | never runs | never runs | never runs | never runs | never runs | never runs | never runs | never runs | Docs only. List | The orchestrator |
| The planner subagent | never runs | never runs | never runs | never runs | never runs | never runs | never runs | never runs | never runs | never runs | runs | never runs | never runs | never runs | never runs | never runs | Docs only. List | The orchestrator |
| The issue-draft subagent | never runs | never runs | runs | runs | never runs | never runs | never runs | never runs | never runs | never runs | never runs | runs | never runs | never runs | never runs | never runs | Docs only. List | The planner subagent |
| The issue-review subagent | never runs | never runs | runs | never runs | runs | never runs | never runs | never runs | never runs | never runs | never runs | never runs | never runs | never runs | never runs | never runs | Docs only. List | The planner subagent |
| The issue-post subagent | never runs | never runs | never runs | never runs | runs | runs | runs | never runs | never runs | never runs | never runs | runs | never runs | never runs | never runs | never runs | Docs only. List | The planner subagent |
| The write subagent of the orchestrator | never runs | never runs | never runs | never runs | runs | never runs | runs | never runs | never runs | never runs | never runs | runs | runs | never runs | never runs | runs | Docs only. List | The orchestrator |
| The opener subagent | runs | never runs | runs | runs | never runs | never runs | never runs | runs | runs | never runs | never runs | never runs | never runs | never runs | never runs | runs | Docs only. List | The orchestrator |
| The reuse subagent | never runs | never runs | runs | runs | never runs | never runs | never runs | runs | runs | never runs | never runs | never runs | never runs | never runs | never runs | runs | Docs only. List | The orchestrator |
| A question session | runs | never runs | runs | runs | runs | never runs | never runs | never runs | runs | runs | never runs | never runs | never runs | never runs | never runs | never runs | Docs only. List | The orchestrator, as its pane owner |
| The plan session of tasker | runs | never runs | runs | runs | never runs | never runs | never runs | never runs | never runs | never runs | runs | runs | never runs | runs | runs | runs | Code of tasker. claude-code: The plan and review roles. codex: The codex provider and What the sandbox blocks and what stays open. pi: The limits of the plan and review roles. Kind pi: docs only for each rule that no seam enforces |
The task subagent that started the run, in the output of tasker |
| The execute session of tasker | runs | never runs | runs | runs | never runs | never runs | never runs | never runs | never runs | never runs | runs | runs | never runs | runs | runs | runs | Code of tasker. claude-code: The execute role. codex: The limits of the execute role. pi: The limits of the execute role. Kind pi: docs only for each rule that no seam enforces |
The task subagent that started the run, in the output of tasker |
| The review session of tasker | runs | never runs | runs | runs | never runs | never runs | never runs | never runs | never runs | never runs | runs | runs | never runs | runs | runs | runs | Code of tasker. claude-code: The plan and review roles. codex: The codex provider and What the sandbox blocks and what stays open. pi: The limits of the plan and review roles. Kind pi: docs only for each rule that no seam enforces |
The task subagent that started the run, in the output of tasker |
Notes on the three session rows. Each cell comes from a statement of assistants.md, or from the rule of the cell
definitions where the doc has no statement.
- K1 runs. The read deny list names the configuration of tasker, so a
taskercommand that reads it cannot run in the shell.assistants.mdnames no limit for a read-only command that reads no configuration, for exampletasker --help, so the rule of the cell definitions gives "runs". - K2 never runs. The read deny list names the configuration of tasker. The shell can write only to the worktree, a temp folder and the write paths of the caller, and the write paths are only places in the clone. A task change changes the state or the record of a task, and the database of the task store lies in the data root, outside these paths.
- K3 runs, because no limit blocks a read in the worktree.
- K4 runs under
claude-code, because the shell writes in its write paths and git data changes throughgitcommands in the shell. Agit pushnever runs. Underclaude-code, the plan and review roles get a deny rule forgit push. In each role, the shell has no ssh agent and no GitHub token, so a push cannot log in. - K5, K6 and K7 never run, because the shell has no GitHub token.
- K8 and K9 never run, because the deny rule of
herdr(plan and review) and the sandbox (execute) stopherdr. - K10 never runs, because the message path between sessions is the
herdrpath, which these limits stop. - K11 runs. The allow list of the execute role holds
AgentandTask.assistants.mdgives no statement for K11 in the plan and review roles, so the rule of the cell definitions gives "runs". - K12 runs under
claude-code, because the shell writes in the write paths of the sandbox, and the plan mode lets the assistant write its plan file. - K13 never runs, because a user-level file is outside the write paths of the sandbox.
- K14 runs under
claude-code. The plan mode does not block a shell command that writes, and the sandbox lets the shell write in the worktree. The execute role also hasEditandWritein the worktree. - K15 runs. The read deny list blocks the credential files only. It names no folder
$HOME/.claude/, and the assistant can read files that the lists do not name. - K16 runs under
claude-code, because the shell runs other commands that the sandbox allows, for example the tests and the npm scripts of the execute session.
Each rule of an orchestration actor is "docs only". The classifier of auto mode decides each call that no rule of Claude
Code matches. The rules of the parent session reach a subagent of the Agent tool, with no flag of the subagent, as
the measured facts show. A session of the kind pi gets only the docs, because its shell runs with
the rights of the user. See The seam of an agent kind.
The ask rules of Claude Code live in the user file. They reach each actor, because the rules of
the parent reach a subagent, as the measured facts show. The ask rules make single commands ask
inside a list, for example tasker abort and tasker update-branch with --undo in the K2 list of a task subagent. No
cell changes for them, unless each command of the list asks. An ask rule adds a prompt to a command. It adds no command
to a list. So tasker approve-credits and the force forms of git push never run for an actor whose list does not name
them.
No row of the table says that a tool enforces a rule. A later ticket can add a PreToolUse hook for one actor at a
time. The measured facts give its start.
Each actor reports a denial to its starter. The starter sends the report on, up to the orchestrator. The orchestrator brings the denial to the user in its question pane. The tool-block rule gives the steps.
A change of the user file changes the row of each session that reads the file. A request for a permission rule of an actor in the user file becomes a request for a new issue. No write subagent starts. See The actor of each write action.
A change of the project file goes through an issue and the tracked-change rule. It waits for the safe way of #957. The reason, in the words of the user: ".claude/settings.json needs to be reserved for development of tasker. On the other hand, orchestrator, including its settings, will be a feature of tasker. So we need to keep that separation as best we can."
A task subagent ran a measure on 2026-11-20 with claude 2.1.330. It ran two claude -p runs. Run 1 used
--permission-mode default. Run 2 differs only in --permission-mode auto. This is the command of run 1:
claude -p --model sonnet --effort low --max-budget-usd 0.5 --permission-mode default --permission-prompts none --no-session-persistence --settings <settings file> --agents <agents file> --output-format stream-json --verbose --forward-subagent-text "Start the subagent probe with the Agent tool. It runs these three commands one by one with its Bash tool: echo ALPHA, then echo BETA, then echo GAMMA. Then it tries to write the file w.txt with the text hi. Report each result in one line."
The settings file had these rules and hooks. The command of each hook is a small script that appends its stdin JSON to a log file:
{
"permissions": {
"allow": ["Bash(echo ALPHA*)"],
"deny": ["Bash(echo BETA*)"]
},
"hooks": {
"PreToolUse": [{ "matcher": "*", "hooks": [{ "type": "command", "command": "<script that appends stdin to a log>" }] }],
"PermissionRequest": [{ "matcher": "*", "hooks": [{ "type": "command", "command": "<same script>" }] }]
}
}The agents file, the value of --agents, had one subagent:
{
"probe": {
"description": "Runs the shell commands that the parent gives it and reports each result.",
"prompt": "You run the shell commands that the parent gives you, one by one, with the Bash tool. Report the exact result or the exact denial of each command. If you have no tool for a step, say so.",
"tools": ["Bash"]
}
}The facts:
- The rules of the parent reached a subagent of the Agent tool, with no flag of its own. In both modes,
echo ALPHAran andecho BETAwas denied in the subagent. - A
PreToolUsehook sawagent_type("probe") andagent_idfor each call of the subagent, in both modes. The call of the parent to the Agent tool had noagent_type. - In auto mode, a shell write (
echo hi > w.txt) ran with no denial. ThePermissionRequesthook did not run, and aPreToolUsehook saw the call. In default mode, the same call needed approval, thePermissionRequesthook ran, and the call was denied. So aPermissionRequesthook misses calls that auto mode allows. A hook that gives each actor its own limits must be aPreToolUsehook. - Not shown: whether a
toolslist of a subagent removes a tool. The probe wrote the file with a Bash redirect and made no Write call. - Not measured: that a failure of a hook denies the call.
echo GAMMAwas meant as a call with no rule. It ran with no prompt in both modes, so it proves nothing.- Cost:
total_cost_usdwas 0.107 and 0.104, about 0.21 USD at the API price. The share of the quota of the user is not measured.
So these facts need no further measure, as the place of the rules says.