parent
bf81241744
commit
9545151b8d
10 changed files with 62 additions and 112 deletions
|
|
@ -103,9 +103,7 @@ there is no such identity to hold a file open for, so the daemon omits
|
|||
anything task-shaped.
|
||||
|
||||
⚠️ This applies to every dispatch, not just role-bearing ones — no agent
|
||||
ships roles yet, so today it's the only path in real use. Before this fix
|
||||
the no-role path put the task straight into the system prompt, same as
|
||||
every `start` before roles existed at all.
|
||||
ships roles yet, so today it's the only path in real use.
|
||||
|
||||
### A role with no file refuses the call
|
||||
|
||||
|
|
@ -356,10 +354,8 @@ Everything else in claude's built-in set is absent, in particular the
|
|||
tools that let a session act outside the run for which it began: peer and
|
||||
operator messaging, nested agents (including the stop verb, which takes
|
||||
an _agent_ id rather than a session), schedule and webhook creation, and
|
||||
worktree switching. Before the harness passed this flag, a subagent
|
||||
reached all of them — `--dangerously-skip-permissions` had removed the
|
||||
only thing that would have asked, and `--allowedTools` would not have
|
||||
helped: it approves prompts in advance rather than restricting anything.
|
||||
worktree switching. `--allowedTools` would not achieve this exclusion on
|
||||
its own: it approves prompts in advance rather than restricting anything.
|
||||
|
||||
One rule worth knowing before editing any of this: **the daemon never
|
||||
emits an empty `--tools` value**, and asserts rather than doing so. Not
|
||||
|
|
|
|||
Loading…
Reference in a new issue