Claude Code’s built-in Task tools vanish server-side

A GitHub bug report describes a failure in Claude Code 2.1.217 and 2.1.218 on macOS arm64: after the TodoWrite-to-Task migration, the built-in task tools sometimes don’t register at all. A ToolSearch for TaskList, TaskCreate, TaskUpdate, and TaskGet came back empty, while 189 other deferred tools were available.
In one 2.1.218 session, four tools loaded and worked at first, then minutes later a system notice said they’d been turned off because “their MCP server disconnected.” TaskStop and TaskOutput stuck around.
The author pulled the binaries for both versions: the Task gating code is identical, and neither the tengu_vellum_ash flag nor the CLAUDE_CODE_ENABLE_TASKS variable disabled anything locally. His conclusion is that exactly those four tools sharing one gate point to flag or registry instability on the server side.
Up next
SharedRoot: escaping the Claude Cowork sandbox on a Mac
Researchers mounted one folder into Claude Cowork, sent a short message, and reached the whole Mac disk: SSH keys, cloud credentials, no permission prompt. The full host mounts into the Linux VM with write access, and a CVE-2026-46331 chain gets root inside it.
Related stories
- A hidden system prompt paragraph tells Claude Code to stop asking permission
- A hardcoded instruction in Claude Code 2.1.219 and 2.1.220 blocks Opus 5 from spawning sub-agents
- Claude Code v2.1.218: /code-review moves to a background subagent
- Claude Code v2.1.217: subagent caps and a memory fix
- Claude Code 2.1.318: login expiry warning, runner log change
- Intent-lens spells out Claude Code calls before they run
Comments
No comments yet. Be the first.
Join the conversation
Sign in to leave a comment. It appears after moderation.

