{"version":"2.1.323","anchor":"late-allow-after-new-input-can-now-be-honoured-in-remote-s","canonical_anchor":"late-allow-after-new-input-can-now-be-honoured-in-remote-s","heading":"An Allow given after you send new input can now still count in remote sessions","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/late-allow-after-new-input-can-now-be-honoured-in-remote-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### An Allow given after you send new input can now still count in remote sessions\n\nIn remote sessions, answering Allow to a waiting permission prompt after sending new input can now be queued instead of dropped\n\n**Unclear.** Whether a given remote session turns this on is decided by the host and not stated.\n\n**What**\n\nA permission prompt asks you whether Claude may take an action. In remote and cloud sessions, if you sent new input while a prompt was still waiting and then answered Allow, that answer used to be dropped. It can now be queued and handled as the result of that action. Running `\/clear` removes it from the queue.\n\nPrompts that come from a connector are now also marked as such.\n\n**Why**\n\nFewer of your approvals are lost in remote and cloud sessions.\n\n- Area: Sessions\n- Names: `\/clear`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}