Feature request: centralized 'all my Claude Code sessions' view across surfaces and devices

Problem

Claude Code now ships on five surfaces — CLI, VS Code, JetBrains, desktop app, and claude.ai/code — and each maintains an independent session list. There is no centralized view that aggregates them. As a heavy user with multiple machines, I currently have no way to answer the question "where are all my Claude Code sessions actually running right now?" without manually checking each surface on each machine.

Concrete example: a quick ps -ax | grep claude on my Mac surfaced two claude processes that had been running for >2 days, including one desktop-agent-mode session resuming a specific session ID that I had completely forgotten about. The fact that I had to use OS-level tools rather than anything inside Claude Code itself is the gap.

Current state (as of Claude Code 2.1.x, May 2026)

• CLI: /resume picker shows sessions on the current machine only. Ctrl+A widens scope from current worktree → all worktrees → all projects, but still single-machine.
• VS Code / JetBrains plugins: maintain their own session history per IDE install, not unified with CLI sessions on the same machine.
• Desktop app: independent session list.
• claude.ai/code (web): server-side sessions tied to the account, not surfaced to local installs.
• Across devices: no aggregation anywhere. claude.ai doesn't show sessions running on the user's local machines, and local installs don't show claude.ai sessions.

Interestingly, the desktop-agent-mode binary has an MCP tool named mcp__ccd_session_mgmt__list_sessions in its allowed-tools list, suggesting a session-listing primitive already exists internally — it's just scoped to that surface.

Proposal

A single view (in the desktop app or at claude.ai) that lists, for the signed-in user:

• All active and recent sessions across devices and surfaces
• Per-session: surface (CLI/VS Code/JetBrains/desktop/web), device/hostname, working directory, model, started-at, last-activity, status (running / idle / terminated)
• Ability to drill into a session's transcript, or send a "please pause/checkpoint and exit" signal to a live session

Why it matters

1. Resource awareness — long-running sessions consume tokens, especially with auto-resume; users should be able to see them.
2. Cost attribution — "which session burned through the budget yesterday?" is currently unanswerable without scraping logs.
3. Continuity — moving between desktop, laptop, and web today means losing track of what you were doing where.
4. Security/audit — for orgs deploying Claude Code, a unified session inventory is a baseline expectation.

Workaround in use today

A user-level slash command at ~/.claude/commands/sessions.md that combines ps -ax | grep claude with a recent-session-files listing under ~/.claude/projects/. Works on one machine; doesn't help across devices.