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.239 ·

Remote tasks stuck waiting on input are failed with a pointer to the cloud UI

A remote task stuck waiting on input now fails as blocked and tells you where to answer it.

You'll notice New Features
JSON All of v2.1.239
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
New FeaturesKind: in v2.1.239,
New FeaturesSection of the release
What

A remote session that keeps asking for something this session cannot answer is now marked failed as "blocked" rather than polling forever, and you are told to answer it in the cloud or relaunch with a permission mode that does not prompt. The gate tengu_coral_anchor defaults to true in the build, so this is live unless remote config turns it off.

Details
  • Stalls are counted only when the remote session reports it requires action and no permission answer is already in flight.
  • The threshold is 3 consecutive stalls, raised to 15 once this session has successfully forwarded an answer at least once.
Evidence

the cloud session is waiting on input (a question, or a permission prompt this session couldn't answer for it).

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Feature flag
tengu_coral_anchor 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.239: on

Read once, for one account on one subscription tier, against v2.1.239. It isn't a statement about your account. What a flag value here can and cannot tell you

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_coral_anchor

See this entry in the whole of v2.1.239 →

Feedback