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 ·

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

In Anthropic cloud sessions a running MCP task stops holding the container up after 168 hours by default, set by tengu_curious_river

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

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.

Read from
Feature flag
tengu_curious_river 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 168 for tengu_curious_river, 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_curious_river, 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 168 for tengu_curious_river, 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_curious_river, 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 168 for tengu_curious_river, 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_curious_river

See this entry in the whole of v2.1.305 →

Feedback