{"version":"2.1.293","anchor":"remote-transport-tracks-queued-command-follow-up-state","canonical_anchor":"remote-transport-tracks-queued-command-follow-up-state","heading":"Remote sessions record whether prompts queued mid-turn got a reply","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/remote-transport-tracks-queued-command-follow-up-state","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Remote sessions record whether prompts queued mid-turn got a reply\n\nIn remote sessions, Claude Code now records for diagnostics whether each prompt queued while it worked was answered, left open or stopped\n\n**What**\n\nWhen Claude Code runs as a remote session, it now looks back through the conversation at each prompt you queued while it was still working. It sorts each one by whether the model replied to it: stopped, open, unread, finished or left. The result goes into its usage reporting. A log entry about permission requests left without an owner also carries more detail.\n\n**Why**\n\nThis is reporting groundwork for remote sessions. It does not change what you see or how prompts are handled.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}