Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.268 ·

Todo/task tool availability no longer conditioned on a remote feature flag

Todo/task tool availability no longer falls back to a remote feature flag; it's decided locally

TierUse it nowhow much it should matter to you
Useful2my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaElsewherewhat it touches
KindImprovementsin v2.1.268,
Use it now

Todo/task tool availability no longer falls back to a remote feature flag; it's decided locally

What

The check that decides whether the todo/task tracking tools are available dropped a remote feature-flag lookup and an associated fallback branch it previously relied on. Now availability is decided purely by local conditions: it's enabled if certain internal checks pass, if the model's capability string is missing or matches specific known patterns, or if the environment variable CLAUDE_CODE_ENABLE_TODO_TOOLS is explicitly set to true, with no separate remote feature-flag fallback anymore.

Why

This makes todo/task tool availability depend only on local, inspectable conditions (the model in use and the CLAUDE_CODE_ENABLE_TODO_TOOLS environment variable) rather than a remote flag fetched from Anthropic's servers.

Read from
Names in the bundleCLAUDE_CODE_ENABLE_TODO_TOOLS
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeChanged the task-tracking tools (TaskCreate/Get/Update/List, TodoWrite) to be offered only on Claude 3.x, Opus 4.0–4.7, Sonnet 4.0–4.6…

See this entry in the whole of v2.1.268 →

Feedback