What
MCP servers are outside tools Claude Code can connect to. This release adds code for an MCP tasks feature, controlled by switches (flags) that Anthropic's server can turn on remotely:
tengu_mcp_tasks: a new check guarding the MCP tasks feature. If the server gives no value, it counts as off. The code that uses this check is not visible in this release.tengu_mcp_task_worker_wake: replacestengu_ccr_context_build_after_resume_enabledat the same places in the code. It now controls how MCP tasks are woken up and retried rather than how context is built after resuming a session. When it is off, the task scheduler skips any task that is not being cancelled, so the wake and retry steps never run. It also guards two other places. It too counts as off if the server gives no value.
No reading has yet been taken of either new switch.
Why
These switches prepare a feature that is not yet active by default. Nothing changes for you unless Anthropic turns the switches on from its side.
tengu_mcp_tasks Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.285: off
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.285. It isn't a statement about your account. What a flag value here can and cannot tell you
What the MCP tasks feature does is not known.
New in this build: tengu_mcp_tasks