## **Problem** The session list in the Duo side panel is a reverse chronological log. Every row gets the same treatment whether the session is running, waiting on you, or finished two days ago. Sessions waiting for input are the highest value thing in the list, and right now they sit mixed in with everything else, flagged only by a status icon on the row. Search, sort and filters help you find a session you already know about. They don't help you notice one you don't. Done also says nothing about whether anything checked the work, so a finished session and a finished-and-verified session look identical. ### **Direction** Treat the list as an inbox, not a history log. State becomes the primary organizing dimension instead of timestamp. Three things a user should be able to answer without opening anything: * What needs me. Waiting for input, approval pending, failed. * What's running. In progress right now, and roughly how far along. * What finished. Done and verified, or done and still needs a look. To support that, a row needs to carry enough to make a decision in place: what ran, what triggered it, current state, how long it's been in that state, what it produced (MR, pipeline, issue), and for finished sessions, what verified it. Some sense of what changed since you last looked, so returning to the panel is a scan and not an audit. One state vocabulary, shared. Running, idle, queued, stuck, done should mean the same thing here as anywhere else agent work is shown, and should hold up for whatever runs next. This is the first step toward sessions being actionable. Once the list knows what needs attention, acting from the list (approve, reject, cancel, retry) is the natural next step rather than a bolt-on. Same controls wherever a session appears. Scoped to the panel, and consistent with the Session observability surface direction. ### **JTBD** When I have sessions running while I work on something else, I want to open the panel and immediately see which ones need me, so I can step in when I'm needed without checking each one. **Supporting** * When several sessions are running at once, I want to tell them apart by state rather than by when they started, so the list orders itself around what matters instead of what's newest. * When a session is blocked on my input or approval, I want to find it without leaving the panel, so I'm not relying on a to-do or an email to tell me something the panel already knows. * When a session has been running longer than expected, I want to see how long it's been in that state, so I can catch a runaway before it burns time or credits. * When a session shows as done, I want to see whether anything verified it, so I know if I need to review it myself. * When I come back to the panel after a while, I want to see what moved since I last looked, so returning is a scan and not an audit. **Out of scope** * Session list on AI \> Sessions. That comes later. * Session details layout. That's the session details panel redesign epic. ### Release target In the first iteration of this work we'll release this to Customer Zero first, prior to promoting to Experimental or Beta.