Summary

Sub-agents spawned via sessions_spawn should inherit the model selected in the user's settings (or session override), rather than requiring hardcoded model assignments per agent.

Current Behavior

• Agents can have hardcoded model field in config
• If omitted, unclear whether they properly inherit the user's default model
• No explicit documentation on model inheritance for sub-agents

Desired Behavior

• Sub-agents with no explicit model config should inherit from:
  1. Parent session's model override (if set via /model or session_status)
  2. agents.defaults.model config
  3. Global default model
• This allows users to switch models once and have all agents follow suit
• Per-agent model overrides should still work when explicitly configured

Use Case

When orchestrating a team of agents (architect, coder, reviewer, devops, tester, docs), users want to:

• Set their preferred model once in settings
• Have all sub-agents use that model automatically
• Not need to update multiple config entries when switching models

Context

Discussed while setting up multi-agent configuration. User expected all agents to follow their model selection without hardcoding each one.