{"version":"2.1.311","anchor":"remote-tasks-inherit-claude-code-task-list-id-dangerous-ski","canonical_anchor":"remote-tasks-inherit-claude-code-task-list-id-dangerous-ski","heading":"Child processes share the task list and no longer inherit permission skipping","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/remote-tasks-inherit-claude-code-task-list-id-dangerous-ski","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Child processes share the task list and no longer inherit permission skipping\n\nProcesses Claude Code starts now get `CLAUDE_CODE_TASK_LIST_ID` and have `CLAUDE_CODE_EVEN_MORE_DANGEROUSLY_SKIP_PERMISSIONS` set to empty\n\n**What**\n\nWhen Claude Code starts another process, it builds the set of environment variables that process sees. That set now includes:\n\n- `CLAUDE_CODE_TASK_LIST_ID`, when the session has a task list\n\n- `CLAUDE_CODE_EVEN_MORE_DANGEROUSLY_SKIP_PERMISSIONS` with an empty value\n\nBefore, no task list ID was passed and the permission-skipping variable was left alone.\n\n**Why**\n\nChild sessions can work from the same task list as the session that started them. Setting the skip-permissions variable to empty stops that override from carrying over, so a child does not bypass permission prompts just because its parent did.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}