Repository navigation
Default model and fallback for subagents in Settings → New threads #33650
Replies: 1 comment
|
+1. I'd like this to include context window, not only model and effort. My case: I run Fable 5.2 at 1M context as the orchestrator. Suggestion for the Sub agent row: let it set options as well as model and effort, with each option either "inherit from parent" or a fixed value (e.g. context window 300k). An explicit option in a |
Uh oh!
There was an error while loading. Please reload this page.
Problem
Settings → New threads already has a default model and a fallback for when that model's provider is out of usage. There's no equivalent for subagents. When an agent calls
delegate_task, the child's model has to come from the prompt or from routing tables in AGENTS.md, which agents copy into every call. If that provider is out of usage, the agent only finds out when the child fails. Related: #28203 (delegated tasks bypass the configured fallback model).Proposal
Add a Sub agent row under Settings → New threads, next to the existing Default agent row:
Each has a reset button, same as the existing rows. An explicit model in a
delegate_taskcall still wins. This setting only fills the gap when none is given.Why settings and not AGENTS.md
Prose routing can't know a provider is out of usage until a child has already failed. The server already tracks usage for the default model's fallback, so it can pick the sub-agent fallback before the child starts. It also works in projects that don't carry routing instructions.
Scope
delegate_taskand scheduled tasks that delegate. Native provider subagents (e.g. Claude's ownAgenttool) keep their own behavior.Looking for maintainer feedback on direction and scope before I open a PR.
All reactions