Plan-continuation (child) sessions never register the task-list tools (CLAUDE_CODE_CHILD_SESSION=1)

Summary

Sessions started via plan mode's "Clear context and continue with plan" run as child sessions (CLAUDE_CODE_CHILD_SESSION=1), and in these sessions the native task-list tools (TaskCreate etc.) are never registered. The model cannot create or maintain the native task list in exactly the sessions that carry an approved multi-step plan — the place a task list matters most.

Environment

• Claude Code 2.1.218, macOS (darwin 25.3.0)
• Reproduced in two independent plan-continuation sessions on 2026-07-23

Steps to reproduce

1. Start a session, enter plan mode, and get a plan approved choosing "Clear context and continue with plan" from the exit menu.
2. In the continuation session, ask Claude to create a task list ("make tasks using the task tools").
3. Claude's tool registry contains no TaskCreate/task-list tool at all — a registry search surfaces only the unrelated background-process tools (TaskOutput, TaskStop). Asking Claude to use the tool fails; there is nothing to call.
4. The session environment shows CLAUDE_CODE_CHILD_SESSION=1.

Expected

Plan-continuation sessions get the task tools (they are the primary consumers of a multi-step task list), or documentation states that child sessions intentionally exclude them and why.

Notes

• Verified no local configuration is responsible: no settings/permissions/hooks on this machine reference or deny the task tools, and the same machine gets task tools normally in regular (non-child) sessions.
• TodoWrite (the older name) does not exist on this install either, so there is no fallback tool.
• Behavior was identical in both sessions tested (the original root-cause session and a retest in a fresh plan-continuation session the next day).

🤖 Generated with Claude Code