{"version":"2.1.305","anchor":"cloud-cap-on-how-long-mcp-tasks-keep-the-container-up-tengu","canonical_anchor":"added-mcp-task-holdcapped-predicate-and-rename-gains-a-cloud","heading":"MCP tasks in cloud sessions stop keeping the container up after a time limit","tier":"soon","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/cloud-cap-on-how-long-mcp-tasks-keep-the-container-up-tengu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### MCP tasks in cloud sessions stop keeping the container up after a time limit\n\nIn Anthropic cloud sessions a running MCP task stops holding the container up after 168 hours by default, set by tengu_curious_river\n\n**What**\n\nAn MCP task is a long-running job started through an MCP server (a connected tool provider). In cloud sessions on Anthropic's infrastructure (`CLAUDE_CODE_REMOTE` true, environment kind unset or `anthropic_cloud`), a running task used to keep the cloud container, the machine the session runs on, up without limit.\n\n- After a number of hours a running `mcp_task` stops keeping the container up. The default is 168 hours (7 days); the server-controlled value `tengu_curious_river` can override it with a number or numeric text.\n\n- At the limit the task is marked `holdCapped`, keeps being checked, and a message says it \"has reached the \u2026 h limit on keeping its cloud container up\".\n\n- The cap is also applied when a session is restored, based on when the task started.\n\n- A task marked `holdCapped` is skipped by one completion notice path.\n\n- Separately, renaming a job in the agent list now records whether it is a cloud job.\n\n**Why**\n\nA forgotten long-running task no longer keeps a cloud session's machine alive indefinitely, but once the limit passes the container may shut down while the task is still running.\n\n- Flag `tengu_curious_river`: Not enough to say (read for one account on one subscription tier against v2.1.305; 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: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}