What probably matters to youSection of the release
What
When a Task worker is launched without an explicit model, it now falls back to a configured default subagent model if one is set, and only then to the model of the session that spawned it. An agent definition's own model setting still wins over both.
Details
Precedence: agent-definition setting, then configured default subagent model, then inherited session model.
With no default configured, behaviour is unchanged from plain inheritance.
Evidence
otherwise omit it so the worker uses the default (the session model, unless a default subagent model is configured)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
