{"version":"2.1.268","anchor":"todotask-tool-availability-no-longer-conditioned-on-a-remot","canonical_anchor":"todotask-tool-availability-no-longer-conditioned-on-a-remot","heading":"Todo\/task tool availability no longer conditioned on a remote feature flag","tier":"use","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/todotask-tool-availability-no-longer-conditioned-on-a-remot","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Todo\/task tool availability no longer conditioned on a remote feature flag\n\nTodo\/task tool availability no longer falls back to a remote feature flag; it's decided locally\n\n**What**\n\nThe 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.\n\n**Why**\n\nThis 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.\n\n- Area: Elsewhere\n- Names: `CLAUDE_CODE_ENABLE_TODO_TOOLS`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 2\/5"}