What
The model field for subagents now says it takes a model alias, a raw model ID, or inherit, and that leaving it unset uses a configured default subagent model, falling back to the parent conversation's model when none is configured.
Details
- The wording implies a separate default-subagent-model setting that applies to every subagent you do not pin.
Evidence
uses the default subagent model when one is configured, else the parent's model
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundleinherit
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Claude apps gateway configuration touched a line naming inherit after this was published.
Set it to `1` only in the policies whose groups you want traced. A policy that doesn't set it inherits the value from your `match: {}` catch-all policy if that policy sets one, per the [merge rules](#managed). To keep a group's clients fro…claude-apps-gateway-config see the edit
Confirmed since
Anthropic's documentation has since written up inherit, on Orchestrate teams of Claude Code sessions.
Teammates start with the lead's permission mode, except [`dontAsk` mode](/docs/en/permission-modes#allow-only-pre-approved-tools-with-dontask-mode), which they don't inherit. If the lead runs with `--dangerously-skip-permissions`, all team…agent-teams see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up inherit, on Orchestrate teams of Claude Code sessions.