{"version":"2.1.311","anchor":"remote-session-held-input-and-resumed-agent-notices","canonical_anchor":"remote-session-held-input-and-resumed-agent-notices","heading":"Cloud sessions can hold your input while a prompt waits, and resume stopped agents","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/remote-session-held-input-and-resumed-agent-notices","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Cloud sessions can hold your input while a prompt waits, and resume stopped agents\n\nCloud sessions can hold typed commands behind a waiting prompt, resume stopped agents automatically, and keep an existing session name\n\n**Unclear.** Which cloud sessions hold typed input behind a waiting prompt is not stated.\n\n**What**\n\nThree changes affect cloud sessions, which run on Anthropic's machines rather than your own:\n\n- Commands you type can be held back while a prompt is still waiting for an answer. Before, only MCP task notices were held back.\n\n- Stopped agents can be resumed automatically from their saved records. An agent here is a helper instance of Claude. Claude is told they will report back by notification when done.\n\n- A remote session is no longer named automatically if it already has a name.\n\n**Why**\n\nThis changes how queued messages and resumed helper agents behave in cloud sessions. An existing session name is kept.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}