{"version":"2.1.248","anchor":"coordinator-workers-can-be-forced-onto-the-session-model","canonical_anchor":"coordinator-workers-can-be-forced-onto-the-session-model","heading":"Coordinator workers can be forced onto the session model","tier":"use","area":"Subagents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/coordinator-workers-can-be-forced-onto-the-session-model","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Coordinator workers can be forced onto the session model\n\nAn env var forces coordinator workers onto the session's model, ignoring any requested one.\n\n**What**\n\nSetting `CLAUDE_CODE_COORDINATOR_FORCE_WORKER_INHERIT_MODEL` makes spawned workers use the session's model no matter what is requested: the coordinator prompt states the model parameter is ignored, the Agent tool marks its `model` parameter unavailable, and the spawn path clears any requested model. It only matters when coordinator mode is on via `CLAUDE_CODE_COORDINATOR_MODE`. Left unset, the prompt merely argues against downshifting workers to weaker models.\n\n**Details**\n\n- The variable is new in this build.\n- Existing code sets and deletes `CLAUDE_CODE_COORDINATOR_MODE` on the process environment itself.\n\n**Evidence**\n\n`- The model parameter is ignored on this session. Do not set it.`\n\n- Area: Subagents\n- Names: `CLAUDE_CODE_COORDINATOR_FORCE_WORKER_INHERIT_MODEL`, `CLAUDE_CODE_COORDINATOR_MODE`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 4\/5"}