/code home Sessions panel selects disconnected sessions and omits connected ones

Summary

The Sessions panel on the /code home (new conversation) screen selects the wrong set of sessions: it omits sessions that are connected and running, and surfaces sessions whose host machine is long gone.

This affects the web UI at claude.ai/code and the Claude desktop app, which renders the same surface. The Claude mobile app is unaffected.

Observed

At the time of writing my account had 25 sessions. Five were connection_status: connected via Remote Control, two of them actively running.

The home panel showed three items. All three were connection_status: disconnected — the machines hosting them no longer exist, so they cannot receive input. Their last events were 30 Jul, 27 Jul and 18 Jun. All three were nevertheless labelled "Requires input" and presented as actionable, each with a "Dismiss session" button.

None of the five connected sessions appeared, including the two running at that moment.

So the panel is inverted with respect to what it should surface:

| | count | connection_status |
|---|---|---|
| shown | 3 | disconnected (dead for weeks) |
| omitted | 5 | connected (2 actively running) |

This is a selection problem, not a sorting one

The panel holds exactly three items in the DOM, with no scroll and no "show more" control. Within those three the ordering is correct — most recent first (3 weeks, 4 weeks, 2 months). The live sessions are not further down the list; they are never selected into it.

The selection appears to key on "awaiting input" alone, ignoring connection_status entirely.

The data is correct — every other surface handles it properly

• GET /v1/code/sessions?statuses=active&statuses=paused returns all 25 sessions with accurate status_bucket, worker_status and connection_status.
• The web sidebar ("Recents") lists them all, with correct live status indicators (running / idle / awaiting input).
• The desktop app sidebar lists them as well, under the "Others" group.
• The Claude mobile app lists them normally.

Regression

This panel previously showed the most recent sessions, on both web and desktop, matching what the mobile app still shows. That was the way to resume work after leaving one machine running and moving to another location. The home screen is now occupied by three dead sessions while the ones that matter are absent.

Steps to reproduce

1. Start a session and enable Remote Control (via /remote-control in an open session, or by running claude remote-control). Both creation paths behave identically.
2. Let it settle into a running or idle state — i.e. not awaiting user input.
3. Open claude.ai/code, or the new-conversation screen of the desktop app.
4. The live session is absent from the Sessions panel. Its direct URL opens and resumes normally, and it is present in the sidebar.
5. Any old session left awaiting input remains listed, even when its host is gone.

Suggested fix

Select on recent activity and connection status rather than on "awaiting input" alone. Disconnected sessions should either be excluded from this panel or marked as unreachable instead of "Requires input".

Environment

• Claude desktop app 1.34493.1 (Windows 11) and browser — same result on two separate machines
• Claude Code CLI 2.1.233 / 2.1.236 / 2.1.237 / 2.1.241 (Ubuntu on WSL2)
• Sessions tagged remote-control-repl, remote-control-sdk, remote-control-cli; environment_kind: bridge

Account and session identifiers omitted here; available privately if useful for triage.