Unclear Which setups get the on-by-default fallback is not clear.
MCP servers are outside programs that give Claude extra tools. Claude Code's support for MCP tasks can now be turned off by setting the environment variable CLAUDE_CODE_DISABLE_MCP_TASKS. An environment variable is a setting you give a program from your shell before starting it. Claude Code also passes this variable on to the programs it starts.
When the variable is not set, a remote switch decides whether MCP task support is on. Before, if the server sent no value, the switch fell back to off. It now falls back to on when several conditions hold, and one of them is that CLAUDE_CODE_REMOTE is not set. When the switch was last read before this release, the server returned it on for this site's account and off for an anonymous account.
One older check that also read this switch now always answers off.
MCP task support appears to be moving from off by default to on by default in some setups. CLAUDE_CODE_DISABLE_MCP_TASKS gives you a reliable way to turn it off if it causes trouble.
tengu_glowing_lark On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: off · compiled default in v2.1.317: 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.
tengu_mcp_task_worker_wake 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.317: 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.317. It isn't a statement about your account. What a flag value here can and cannot tell you
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.
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.
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.
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.
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.
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.
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.
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.
Which setups get the on-by-default fallback is not clear.
New in this build: CLAUDE_CODE_DISABLE_MCP_TASKS