[DOCS] Sub-agents resume section omits that an explicit model selection persists across resume and follow-up

Status Fixed / completed
Maintainer reply None cached
Activity 1 comment · opened Jul 16, 2026 · closed Aug 17, 2026

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/sub-agents

Section/Topic

"Resume subagents" and "Choose a model" (model resolution order).

Current Documentation

The resume section says:

Resumed subagents retain their full conversation history, including all previous tool calls, results, and reasoning. The subagent picks up exactly where it stopped rather than starting fresh.

The model section explains resolution when a subagent is first invoked (environment variable, per-invocation parameter, frontmatter, main conversation model) but does not state what model applies when the same subagent is resumed or sent a follow-up message.

What's Wrong or Missing?

Claude Code v2.1.211 fixed subagents spawned with an explicit model override reverting to the parent's model when resumed or sent a follow-up message. Users selecting a model explicitly for a subagent need to know that the selected model continues to apply on resume and follow-up, not only on the first spawn.

Suggested Improvement

Under "Resume subagents", add:

Resuming or sending a follow-up to a subagent keeps the explicit model selected for the original spawn. It does not revert to the main conversation's model.

Under "Choose a model", add a bullet in the resolution list clarifying that resume and follow-up messages reuse the explicit model selected for that agent instance.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:
| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/sub-agents | 290–308, 848–878 | Model resolution and resume subagents |

Total scope: 1 page affected

Version: v2.1.211 fix clarifies expected persistence behavior.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗