{"version":"2.1.281","anchor":"remote-tasks-stop-waiting-when-the-cloud-session-is-stuck-on","canonical_anchor":"remote-tasks-stop-waiting-when-the-cloud-session-is-stuck-on","heading":"Remote tasks stop waiting when the cloud session is stuck on MCP server questions","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/remote-tasks-stop-waiting-when-the-cloud-session-is-stuck-on","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Remote tasks stop waiting when the cloud session is stuck on MCP server questions\n\nA remote task stops waiting and is marked blocked when its cloud session has unanswered MCP server questions for too long\n\n**What**\n\nWhen you start a task that runs in a cloud session, your local session keeps checking on it. An MCP server (an outside tool the session is connected to) can stop that cloud session to ask a question. If the task is waiting on such a question, your local copy of the task now stops waiting and is marked failed or blocked in either of two cases:\n\n- one question has gone unanswered for 10 minutes\n\n- new questions have kept arriving for more than 30 minutes\n\nThe message says these questions can't be answered from your local session and tells you to answer them on the cloud session's page, where that session will carry on. Other kinds of waiting keep their old wording.\n\n**Why**\n\nYour local session no longer waits forever on a question it cannot answer. You are told where to go to unblock the task.\n\n- Flag `tengu_coral_anchor`: Not enough to say (read for one account on one subscription tier against v2.1.281; this account: no value returned, anonymous baseline: no value returned, compiled default: on) 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."}