Claude/Code/Q/If I rename a CLI session with /rename, can I resume it in Claude Desktop's Code tab?
If I rename a Claude/Code CLI session with /rename, can I resume it in Claude/Desktop/Code?
- Answer/Official from Manage sessions and Desktop application:
- Short answer: No.
/rename creates a resume handle that only the CLI honors, and the Code tab keeps a session history of its own — a CLI session never appears in its sidebar, named or not. The one bridge runs the other way: /desktop hands the live CLI session over to the app. - What
/rename buys you, and where: the name shows on the prompt bar and in the /resume picker, and becomes a resume handle — claude --resume <name> or /resume <name>, resolved across the current repository and its worktrees. It replaces the AI-generated session title, which is display-only and is not a resume handle. - Why the Code tab can't see it: the docs state plainly that the desktop app, Claude Code on the web, and the VS Code extension "each maintain their own session history." The CLI–Desktop relationship is spelled out under Coming from the CLI?: both can run at once on the same machine and even the same project, and "Each maintains separate session history, but they share configuration and project memory via
CLAUDE.md files." Config and memory are shared; the session list is not. - There is no
/resume in the Code tab to begin with. The CLI-flag equivalence table maps --resume / --continue to "Click a session in the sidebar" — and that sidebar is a list of Desktop's own sessions, filterable by status, project, and environment, with no picker or search that reaches into CLI history. - Rename direction that does cross over: renaming a Remote Control session from claude.ai or the Claude app applies the same name in the CLI (needs Claude Code v2.1.221+). The Desktop equivalent does not reciprocate — per the docs, "a desktop-app session resumes in the app, which keeps its own session history."
- The actual bridge —
/desktop: run it in the terminal and Claude saves the session, opens it in the desktop app, and exits the CLI. Constraints: macOS and x64 Windows, signed in with a Claude subscription; unavailable with API-key auth or on Amazon Bedrock, Google Cloud's Agent Platform, and Microsoft Foundry. It is a one-way handoff of the session you are sitting in — not a picker for arbitrary past CLI sessions. - A structural reason beyond the store split: every Code tab session in a git repository gets its own isolated worktree under
<project-root>/.claude/worktrees/ (see git/worktree), plus the status, PR, and environment metadata the sidebar filters, groups, and auto-archives on. A plain CLI session carries none of that, so there is nothing for the sidebar to file it under. - Observed locally, undocumented: CLI transcripts live at
~/.claude/projects/<project>/<session-id>.jsonl, and /rename is recorded inside that transcript as a custom-title entry — so the name travels with the file, which is why the CLI can resolve it from any directory. Desktop tracks its Code tab sessions in a separate registry keyed by local_-prefixed ids. The transcript entry format is documented as internal and subject to change between releases, so don't build on it. - Wanted, not shipped: open requests cover this exactly — Desktop app should list and resume CLI sessions from ~/.claude/projects/ and Sync sessions across Claude Code CLI, Desktop app, and web.