Feature request: Unified session history across CLI, Desktop app, VS Code, and Web
Status Fixed / completed
Maintainer reply None cached
Activity 4 comments · opened Apr 17, 2026 · closed Apr 27, 2026
Currently, Claude Code sessions are siloed by client:
- Terminal CLI sessions don't appear in the Desktop app
- VS Code extension sessions are separate
- Web (claude.ai/code) sessions are isolated
There is no way to view all sessions from a single account in one place.
For comparison, OpenAI Codex syncs all sessions across its app regardless of where they were started.
Expected behavior: All Claude Code sessions tied to the same account should be visible and searchable from any client (Desktop app, CLI, VS Code, Web).
Why this matters: When working across multiple terminals, IDE, and desktop app throughout the day, it's difficult to find and reference past sessions.
4 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Related observation from SSH remote mode specifically (Claude for Mac 1.3109.0 → Claude Code 2.1.112 on Linux):
Connecting to a remote host via Claude Desktop's SSH remote feature doesn't show any existing
claudeCLI sessions that live on that remote host's filesystem (~/.claude/projects/). You can only start a new session — no way to browse or resume sessions that are right there on the same machine.Codex's SSH remote behaves the opposite way: it lists all sessions from the remote host on connect, making them directly resumable.
This feels like a narrower, local version of what you're describing. Even without cross-machine account-wide sync, SSH remote could at minimum surface the sessions physically present on the machine it's connecting to.
(Also filed #49790 on the related session-lifecycle issue — SSH remote session dies when the client disconnects.)
This needs to happen ASAP!
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.