{"version":"2.1.311","anchor":"team-lead-process-recorded-clear-keeps-task-list-link","canonical_anchor":"team-lead-process-recorded-clear-keeps-task-list-link","heading":"Task lists stay linked after \/clear , and teams record their lead process","tier":"notice","area":"Agent Teams","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/team-lead-process-recorded-clear-keeps-task-list-link","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Task lists stay linked after `\/clear`, and teams record their lead process\n\nClaude Code now notes the task list of a session you clear with \/clear, and records which process leads a team\n\n**What**\n\n`\/clear` starts a new conversation with empty context. A task list is the list of to-dos Claude keeps while working. Claude Code now writes a `.session-list` file noting the task list of the session that was cleared. If it cannot, it reports that it \"Could not note the task list of the cleared session\".\n\nWhen a team of agents is set up, Claude Code now records which process leads the team. It also reads the environment variable `CLAUDE_INTERNAL_SESSION_TASK_LIST_ID` and then removes it.\n\n**Why**\n\nTask lists can now carry on across `\/clear` and across creating a team, instead of being lost.\n\n- Area: Agent Teams\n- Names: `\/clear`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}