{"version":"2.1.269","anchor":"new-idle-terminal-status-for-bridgeremote-control-session","canonical_anchor":"new-idle-terminal-status-for-bridgeremote-control-session","heading":"New 'idle' status for background sessions and the remote-control bridge","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/new-idle-terminal-status-for-bridgeremote-control-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### New 'idle' status for background sessions and the remote-control bridge\n\nSessions now have an explicit idle status, both in status reporting and in the remote-control bridge lifecycle\n\n**What**\n\n- A new status reporter maps session state (running, requires_action, idle) to a coarser status of busy, waiting, or idle, and for waiting sessions adds a detail string of either \"input needed\" or \"permission prompt\" depending on what the session is waiting on. Repeated identical updates are no longer re-sent.\n\n- The remote-control bridge session lifecycle now recognizes a distinct 'idle' exit status, separate from completed, failed, or interrupted. An idle session is parked rather than torn down or archived, and the server re-queues it the next time a message arrives.\n\n**Why** This gives a clearer, de-duplicated picture of whether a background or remote-controlled session is actively working, waiting on the user, or simply idle, and keeps idle sessions available to resume instead of ending them.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}