Task/Todo tools (TaskCreate/TodoWrite) not exposed despite `todoFeatureEnabled: true` — regressed ~2026-07-21, appears account-gated

Additional info for duplicate #80213 - I have a Max subscription.

Additionally - tried the downgrade option, and that did not resolve the issue.

Follow-up: I directly tested the Agent Teams hypothesis from the original report and can now rule it out by experiment, not just by inference.

Test (2026-07-23): removed CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS from both scopes where it was set — ~/.claude/settings.json and the project .claude/settings.json — then started a fresh session.

Note for anyone reproducing: the settings .env block re-asserts this variable over a shell-level CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=0, so a shell override is not sufficient. It has to be removed from every settings scope.

Result, in one session (v2.1.218):

! echo "teams=[$CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS]"
teams=[]

ToolSearch({query: "select:TaskCreate,TaskUpdate,TaskList,TodoWrite"})
No matching deferred tools found

Agent Teams off, todoFeatureEnabled: true, CLAUDE_CODE_ENABLE_TASKS unset — and the Task/Todo tools are still not exposed. The setting has since been restored.

Also reproduced on 2.1.218, so the version list is now 2.1.216 / 2.1.217 / 2.1.218.

Updated status of every hypothesis:

| Hypothesis | Status |
|---|---|
| CLI version | Ruled out — 2.1.216 exposed the tool on 07-21 and does not now |
| Model | Ruled out — Opus 4.8 and Sonnet 5 both affected |
| Terminal / wrapper | Ruled out — cmux, Warp, Terminal.app all affected |
| todoFeatureEnabled | Ruled out — it is true |
| CLAUDE_CODE_ENABLE_TASKS | Ruled out — unset; gate returns enabled |
| CLAUDE_CODE_CHILD_SESSION | Ruled out — non-child terminals affected too |
| Agent Teams | Ruled out — directly tested above |

Every local variable I can control has now been eliminated. Unless I'm missing a client-side gate that isn't in settings or env, this looks account-scoped and server-resolved. Happy to run any specific diagnostic or provide transcript excerpts if that would help narrow it.

I see multiple people reporting this issue how. Great. It came out of nowhere. They need to fix this.

Ths remains, SHAMEFULLY, broken today in the latest build:

TaskCreate is not available in this session. The search loaded some similarly named tools, but none of them is it:

• TaskOutput — retrieves output from a running/completed background task (shell, agent, remote session)
• TaskStop — stops a running background task by ID

These are for managing background processes, not task lists. TaskCreate, TaskUpdate, and TaskList — the task-list tools that the framework rules reference (e.g., the /work execution rule's two-phase task creation and compaction-recovery pattern) — don't exist in this harness build, and no equivalent todo-list tool (like TodoWrite) is present either.

I just discovered this and it worked for me:

Try this (or equivalent for your environment):

"env": {
"CLAUDE_CODE_ENABLE_TASKS": "true",
"ENABLE_TOOL_SEARCH": "false"
},

Task tracking
TaskCreate, TaskList, TaskGet, TaskUpdate — present and verified working this session

For me it just started working again. WTH.

Update from my side: the tools started working again on their own, mid-session, without applying any workaround.

Full sequence observed inside a single session:

1. Session started with TaskCreate / TaskUpdate / TaskList / TaskGet present, but only in the deferred tool pool (i.e. loadable on demand via ToolSearch, not in the main tool list).
2. Mid-session the harness announced them as "no longer available (their MCP server disconnected)", and a ToolSearch for select:TaskCreate,TaskUpdate returned "No matching deferred tools found".
3. Later in the same session the harness announced "4 deferred tools are available again", and TaskCreate / TaskUpdate worked normally from then on.

Closing this. The tools have been working consistently since 27 July, without applying any workaround.

Confirmed again today: ToolSearch("select:TaskCreate,TaskUpdate") returns both schemas and real calls succeed. Worth noting for anyone who lands here, they're exposed as deferred tools rather than top level, so they don't show up in the tool list until you search for them. That looks identical to "missing" if you don't know to look.