Unified sessions, settings & projects across Desktop, Mobile and CLI
Status Open
Maintainer reply None cached
Activity 6 comments · opened Apr 1, 2026
Feature Request
I'd love to have a unified experience across all Claude Code surfaces (Desktop app, Mobile, CLI). Currently, sessions, projects, and some features are isolated per interface.
What I'd like to see
- Sessions: Access and resume the same sessions across Desktop, Mobile, and CLI — not just transfer, but true sync
- Projects: See all projects regardless of which surface they were created in
- Settings & configuration: Already mostly shared (MCP servers, CLAUDE.md, hooks, permissions) — this is great, please keep it that way
- Feature parity: Where technically possible, the same features should be available on all surfaces
Why this matters
Switching between CLI and Desktop (or Mobile) currently means losing context. A unified session and project layer would make it seamless to start work on the CLI and continue on Desktop or Mobile without friction.
Current state
- Settings (MCP, CLAUDE.md, hooks, permissions): shared ✅
- Sessions: isolated per surface ❌
- Project overview: isolated per surface ❌
- Session management (browse, delete, archive): only available on web ❌
6 Comments
+1 on this. Two specific CLI features I miss most on the desktop app:
opusplanor manually switch models between planning and execution; the desktop app has no equivalent. See #47985 for theplanModelfeature request specifically.Both represent real cost/quality wins that desktop users can't access today.
+1 — this is even more pressing as of last week.
OpenAI shipped exactly this for Codex on May 14, 2026 ("Work with Codex from anywhere"). The mobile experience is: scan a QR from Codex for Mac once, and from then on every thread on the desktop is automatically mirrored to the ChatGPT mobile app — review outputs, approve commands, switch models, start new tasks, all without touching the laptop.
Claude Code's current
/remote-controlmodel is opt-in per session from the CLI, which means:For users who actually want to step away from the desk and keep agentic work moving (the explicit use case Claude Code is being positioned for), the "opt-in per session" gate is now the dominant friction point versus the competitor.
Concrete ask, aligned with the original issue: default to syncing all sessions across surfaces (with a privacy opt-out for sensitive projects), not the other way around.
Refs:
+1 as was mentioned in this request you can't view chats started in the VS code extension inside of Claude Code on the desktop app, which is unintuitive. There's another similar request here. Being able to see the full chat history for Claude Code, wherever you use Claude Code on your computer, would be a much improved experience!
Adding the Cowork <-> Claude Code gap to this request:
Strong +1. One concrete case not fully covered above: agent sessions I run in Cowork (desktop app) do not appear in the Claude Code VS Code extension's "Web" mode. That "Web" option connects to claude.ai/code (repo-based Claude Code), and the Cowork agent list is not surfaced there. Cowork only syncs across its own surfaces (desktop/web/mobile).
So the isolation isn't just CLI vs Desktop vs Mobile; it's also Cowork vs Claude Code under the same account (related: #62321). As already noted in this thread, OpenAI Codex + the ChatGPT app expose one unified session history regardless of where a session started. Please include Cowork sessions in the unified session/agent history, not only Claude Code surfaces.
+1, hitting this exact gap.
Using the VS Code extension for a session and then switching to the desktop app or claude.ai (Web) with the same account — the session doesn't show up at all. Each surface (CLI, VS Code extension, Desktop app, Web) seems to keep its history completely siloed, even though authentication/config (MCP servers, CLAUDE.md, hooks, permissions) is already shared account-wide.
Would really like to see session history (not just settings) synced/visible across all official surfaces for the same account, as described above. Local-first with an opt-in cloud sync (as suggested elsewhere) would already solve most of the pain.
+1! I work across Mac and PC and not being able to see the same Chat sessions and switch from one to the other is a huge pain!!