MCP tasks in cloud sessions stop keeping the container up after a time limit

What

An 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.

• 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.
• At the limit the task is marked holdCapped, keeps being checked, and a message says it "has reached the … h limit on keeping its cloud container up".
• The cap is also applied when a session is restored, based on when the task started.
• A task marked holdCapped is skipped by one completion notice path.
• Separately, renaming a job in the agent list now records whether it is a cloud job.

Why

A 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.