{"version":"2.1.317","anchor":"cloud-queued-prompt-controller-is-constructed-with-a-not-s","canonical_anchor":"cloud-queued-prompt-controller-is-constructed-with-a-not-s","heading":"A prompt typed while a cloud session starts can be sent once start-up finishes","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/cloud-queued-prompt-controller-is-constructed-with-a-not-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### A prompt typed while a cloud session starts can be sent once start-up finishes\n\nA prompt typed while a cloud session is starting is kept as a draft and sent automatically when start-up ends, or held back with a reason\n\n**Unclear.** When a cloud session starts with a prompt that this applies to is not stated.\n\n**What**\n\nWhen a cloud session, one that runs on a remote machine, is starting, Claude Code can keep the first prompt in the draft box and send it automatically once start-up finishes. While waiting it shows: \"Your message will be sent once start-up finishes. No need to press Enter.\"\n\nIt can instead hold the prompt back, with a message for each case:\n\n- Your organization's settings have not been approved.\n\n- There are launch warnings.\n\n- A question is waiting behind the draft.\n\n**Why**\n\nIt changes what happens to a prompt you type while creating a cloud session: it is either sent for you or deliberately kept back.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}