Smith::Subagents::Supervisor

The main agent is depth 0, so this allows three levels of children.

The supervisor a child agent would need in order to delegate further. Nothing registers the agent tool for children today, so this is currently only reached from the specs — but the limits are wired here, so whoever does register it (see #21) inherits them instead of reinventing them.

Whether a child of this supervisor could itself delegate. Used to decide whether offering the agent tool is worth the tokens.

Plan mode is a property of the whole run, not just the main thread: without this, agent(mode: "work") would be a trivial way around it.

Plan mode is a property of the whole run, not just the main thread: without this, agent(mode: "work") would be a trivial way around it.

Children build their own registry, so without the approver a work-mode subagent would run bash straight past the parent's approval gate.

node_path is this supervisor's own position ("2.1"), which its children extend — an id is then unambiguous across levels. A definition may name a different provider, but building one needs API keys and config that belong in the CLI — so the CLI injects a factory rather than having that logic duplicated here.

Children build their own registry, so without the approver a work-mode subagent would run bash straight past the parent's approval gate.

node_path is this supervisor's own position ("2.1"), which its children extend — an id is then unambiguous across levels. A definition may name a different provider, but building one needs API keys and config that belong in the CLI — so the CLI injects a factory rather than having that logic duplicated here.