{"version":"2.1.311","anchor":"cloud-sessions-user-messages-held-while-a-turn-is-running","canonical_anchor":"cloud-sessions-user-messages-held-while-a-turn-is-running","heading":"Cloud sessions hold your messages while loading and show the session's name","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/cloud-sessions-user-messages-held-while-a-turn-is-running","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Cloud sessions hold your messages while loading and show the session's name\n\nIn cloud sessions, messages you send while the session is loading are held and added once it connects, and the session's name appears in the status view\n\n**Unclear.** It is not clear what decides whether messages are held, so it may not apply to every cloud session.\n\n**What**\n\nA cloud session runs on remote machines instead of your own computer. Two things change in how Claude Code handles one.\n\n- Messages you send while the session is still loading are now held back instead of being added straight away. Held messages are added when the session connects or reconnects, when it is reset, and when the waiting queue is cleared.\n\n- Claude Code now tracks the cloud session's name and follows it when the name changes. The name is shown as a row in the status view.\n\nBefore this change, messages were added straight away and no session name was kept.\n\n**Why**\n\nThis changes how messages you type and the session's name behave in cloud and remote sessions.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}