{"version":"2.1.299","anchor":"tengu-mcp-tasks-check-hardcoded-to-false","canonical_anchor":"tengu-mcp-tasks-check-hardcoded-to-false","heading":"MCP tasks feature is now fixed off and can no longer be turned on remotely","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/tengu-mcp-tasks-check-hardcoded-to-false","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### MCP tasks feature is now fixed off and can no longer be turned on remotely\n\nClaude Code no longer checks a remote switch for MCP tasks and treats the feature as off for everyone\n\n**Unclear.** Which parts of MCP task support this switch controlled.\n\n**What**\n\nMCP servers are add-ons that give Claude Code extra tools, using the Model Context Protocol. A feature related to MCP tasks, longer jobs run through those servers, used to be controlled by a remote switch that was off unless turned on from the server. Claude Code no longer checks that switch and treats the feature as off in every case.\n\n**Why**\n\nThe feature can no longer be turned on remotely in this build.\n\n- Flag `tengu_mcp_tasks`: Not enough to say (read for one account on one subscription tier against v2.1.299; this account: no value returned, anonymous baseline: no value returned, compiled default: 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.\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}