What
- 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.
- 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.
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.