Claude Code Desktop 2026 Redesign — Multi-Agent Work, Native on the Desktop
Mission Control sidebar, parallel sessions with split panels, integrated terminal + editor, rebuilt diff viewer, SSH on Mac, plugin parity with CLI. Available to Pro/Max/Team/Enterprise.
Mission Control — Every Session in One View
Mission Control is the centerpiece of the redesign. The left sidebar lists every active and recent session, filterable by status (running/idle/error), project, and environment (local/cloud). Where you used to juggle terminal windows, you now scan the whole picture in one pane. Click into any session for context, file changes, and command history. This is the step that turns Claude Code from a command-line tool into something closer to an operating system for AI work.
Parallel Sessions, Split Panels, Integrated Terminal
The new desktop natively supports multiple parallel sessions. Split-panel mode shows two sessions side by side (e.g. one rewriting auth, another running tests). Each session has its own integrated terminal (run pytest / npm test inline) and an in-app file editor (spot edits without switching to VS Code). Pairs naturally with git worktree isolation (see our Worktree guide).
Rebuilt Diff Viewer, Expanded Preview, Mac SSH
The diff viewer was rewritten for large changesets — hundreds of files scroll without lag, with inline blame and syntax-aware diff. The preview pane now handles local HTML, PDF, and running app servers (auto-detects local ports like :3000 / :8080) so you don't switch to a browser. SSH support, previously Linux-only, is now on macOS — connect to a remote dev box directly from Claude Code Desktop, no VS Code Remote in between.
Plugin Parity With the CLI
Before the redesign, plugin behavior diverged: org-managed or locally installed plugins worked in CLI but might not in desktop. Parity now means anything installed in CLI shows up in desktop, and org-level marketplace configuration is shared. Pair this with the official Anthropic directory (see Plugin Marketplace 2026) and projected context cost display, and your plugin selection workflow is uniform across surfaces.
FAQ
Desktop or Terminal CLI?
Desktop wins for visual-heavy tasks: diff review, multi-session overview, PDF/HTML preview. CLI wins for scripting, CI integration, and the long tail of flags (--max-turns / --output-format) the desktop doesn't expose yet. Daily dev → desktop; automation → CLI.
How do I configure SSH on Mac? Anything extra needed?
The new desktop ships a built-in SSH client. Add a host in settings and you're done — no VS Code Remote required. Authentication supports password and key (put the key in ~/.ssh/). Linux always had this; Mac is the new addition.
Can I use Claude Code Desktop from China?
The desktop is a local client. Route model traffic through QCode.cc for transparent in-China access, and all local features — Mission Control, parallel sessions, plugins — work identically to overseas users.
Run Claude Code Desktop Through QCode
Transparent access to all Claude models from China; Mission Control multi-session experience matches overseas users.
Start Your QCode Plan