Session dashboard — view and connect to all active Claude Code instances from claude.ai/mobile

Problem

When I open claude.ai on my phone, I expected to see all my running Claude Code terminal sessions and be able to jump into any of them. Instead, /claude-server only creates a single new isolated session with a specific URL. There's no way to discover or connect to existing Claude Code instances running on my machine.

My workflow involves multiple Claude Code sessions across different projects simultaneously. Being able to check in on them, see progress, and send follow-up instructions from my phone would be a huge productivity unlock — especially for long-running tasks.

Proposed solution

A session registry that lets claude.ai (and mobile) show a list of all active Claude Code instances on a machine.

Implementation sketch

1. Session registry — Each Claude Code instance registers itself on startup (pid, project directory, status, start time, current task summary) to a well-known location like ~/.claude/sessions/. Deregisters on exit, with stale entry cleanup for unexpected exits.

1. Optional remote-control opt-in — A global setting or flag (--discoverable) that makes a running instance available for remote connection, not just instances started via /claude-server. This would start the WebSocket listener on an existing session rather than requiring a separate server.

1. Session list API — A local endpoint (or the existing remote control auth flow) that returns all registered sessions, queryable by claude.ai.

1. Session picker UI — When connecting from claude.ai or mobile, show a dashboard of active sessions with:

• Project name / working directory
• How long it's been running
• Last activity / current task
• Status (idle, working, waiting for input)
• Click to connect

Why this matters

• Claude Code sessions often run long tasks (test suites, multi-file refactors, deployments). Being able to check in from a phone without needing SSH/tmux is the natural UX.
• The remote control infrastructure already exists — this is mostly a discovery and presentation layer on top of it.
• It turns Claude Code from a "sit at your desk" tool into something you can manage on the go.

Additional context

• Local-only (single machine) would be a great v1. Cross-machine discovery could come later via Tailscale, relay, etc.
• Security: the existing remote control auth model should extend naturally to multi-session access.