{"version":"2.1.311","anchor":"task-list-id-resolution-gains-session-level-setting","canonical_anchor":"task-list-id-resolution-gains-session-level-setting","heading":"Shared task list choice can come from a session setting","tier":"notice","area":"Agent Teams","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/task-list-id-resolution-gains-session-level-setting","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Shared task list choice can come from a session setting\n\nClaude Code now picks which shared task list to use from session settings, preferring a session list id over the team name for team members\n\n**Unclear.** It is not stated whether `taskList.sessionListId` is something you set yourself or something Claude Code fills in.\n\n**What**\n\nClaude Code keeps a task list, a shared list of to-do items that Claude and its helper agents track and update. The way it decides which list a session uses has changed:\n\n- `CLAUDE_CODE_TASK_LIST_ID` is still checked first, as before.\n\n- After that, Claude Code reads `taskList.sessionListId` and `taskList.leaderTeamName` from its settings.\n\n- For a team member (one of several agents working together as a team), a session list id now takes priority over the team name. Before, a team member always used the team's name.\n\nTaskUpdate, the tool Claude uses to change an existing task, also handles task dependencies differently. When it marks that a task blocks another, or is blocked by another, it now goes through only the newly added task ids instead of the whole list.\n\n**Why**\n\nThis changes which shared task list a session or teammate ends up working from. If you rely on teammates sharing one list, a session list id can now steer a teammate to a different one.\n\n- Area: Agent Teams\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}