{"version":"2.1.233","anchor":"teammates-are-only-told-about-the-task-list-when-they-can-us","canonical_anchor":"teammates-are-only-told-about-the-task-list-when-they-can-us","heading":"Teammates are only told about the task list when they can use it","tier":"notice","area":"Subagents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/teammates-are-only-told-about-the-task-list-when-they-can-us","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### Teammates are only told about the task list when they can use it\n\nSpawned teammates only hear about the shared task list when they actually have task tools.\n\n**What**\n\nThe instructions given to a spawned teammate now depend on whether that teammate actually has task tools. The task-list path and the line \"Check the task list periodically. Create new tasks when work should be divided. Mark tasks resolved when complete.\" are only added when it does; previously both were sent unconditionally. A teammate without task tools also stops auto-claiming the next open task.\n\n**Details**\n\n- A `hasTaskListTools` field on the team context attachment carries the answer, computed from the teammate's real tool surface.\n- Task tooling is gated: `CLAUDE_CODE_ENABLE_TASKS` can force it off, and the todo\/task surface otherwise falls back to `tengu_rosy_wren`, which is false in this build.\n\n**Evidence**\n\n`hasTaskListTools`\n\n- Area: Subagents\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}