{"version":"2.1.251","anchor":"workflow-spawned-agents-resolve-their-own-model-before-inher","canonical_anchor":"workflow-spawned-agents-resolve-their-own-model-before-inher","heading":"Workflow-spawned agents resolve their own model before inheriting","tier":"internal","area":"Workflows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/workflow-spawned-agents-resolve-their-own-model-before-inher","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Workflow-spawned agents resolve their own model before inheriting\n\nWorkflow-spawned agents resolve a model themselves before falling back to the main one.\n\n**What**\n\nAn agent started by a workflow used to always take the main loop's model when none was given. It now consults a model resolution step first and only falls back to the main loop model when that step says \"inherit\". An explicit model on the call still wins.\n\n**Details**\n\n- What the resolution step reads, and so what makes it return something other than \"inherit\", is not visible in the shipped code.\n\n**Evidence**\n\n`N !== \"inherit\" ? N : F.options.mainLoopModel`\n\n- Area: Workflows\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}