{"version":"2.1.281","anchor":"cloud-agent-runs-handling-of-sessions-waiting-on-input","canonical_anchor":"cloud-agent-runs-handling-of-sessions-waiting-on-input","heading":"Cloud agent runs: handling of sessions waiting on input","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/cloud-agent-runs-handling-of-sessions-waiting-on-input","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Cloud agent runs: handling of sessions waiting on input\n\nCloud agent runs that stop to wait for input now wait up to 10 minutes for an MCP question and fail quickly for any other kind of prompt\n\n**What**\n\nWhen 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:\n\n- 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.\n\n- Any other pending prompt: the run fails right away.\n\n- No pending action listed at all: the run fails after 3 checks in a row.\n\nThe message shown at the 30-minute timeout also says so if an MCP question was still unanswered.\n\n**Why**\n\nA cloud run that is stuck waiting for someone to answer now ends with a clear reason. It no longer just runs out the clock.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}