You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
ImprovementsKind: in v2.1.281,
ImprovementsSection of the release
What
When Claude Code checks on a session running in the cloud and finds it waiting for input (status requires_action), it now looks at what the session is waiting for:
An MCP server question (dialog:mcp_elicitation): Claude Code keeps waiting for up to 10 minutes (600000 ms) on that same question, then stops with an error explaining why.
Any other pending prompt: the run fails right away.
No pending action listed at all: the run fails after 3 checks in a row.
The message shown at the 30-minute timeout also says so if an MCP question was still unanswered.
Why
A cloud run that is stuck waiting for someone to answer now ends with a clear reason. It no longer just runs out the clock.
