Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.305 ·

Tasks can be turned off for named MCP servers by a remote list

A server-sent list can now turn off Tasks for named MCP servers, whose tool calls then run without Tasks; the list is empty by default

Nothing to try yet In Development
JSON All of v2.1.305
Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
MCPArea: what it touches
In DevelopmentKind: in v2.1.305,
In DevelopmentSection of the release
What

MCP servers are outside programs that give Claude extra tools. Before Claude Code calls one of their tools, it now checks a list of servers sent by Anthropic through the switch tengu_gleaming_creek. If the server is on the list, Tasks is turned off for it and its tool calls run without Tasks, and a debug log line says so. Previously only a general check decided whether Tasks were used. When nothing is sent, the list is empty and no server is excluded.

MCP tool calls also gained a timeout that can be restarted while a call is running, and a second way for a call to be cancelled.

Why

Anthropic can now switch Tasks off for a particular MCP server without affecting the others. If an MCP server's tool calls behave differently, the debug log tells you whether this list is the reason.

Read from
Feature flag
tengu_gleaming_creek Not enough to say

Nothing 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.305: not a boolean we can read

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.305. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns [] for tengu_gleaming_creek, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_gleaming_creek, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns [] for tengu_gleaming_creek, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_gleaming_creek, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns [] for tengu_gleaming_creek, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_gleaming_creek

See this entry in the whole of v2.1.305 →

Feedback