Existing Claude Code sessions do not appear resumable from Claude App Code

Status Closed — not planned
Reported on v2.1.216
Maintainer reply None cached
Activity 1 comment · opened Jul 22, 2026 · closed Jul 22, 2026

Existing Claude Code sessions do not appear resumable from Claude App Code

Summary

I want to continue an existing local Claude Code session from Claude App's Code view. The app can see my local Code stats and project folders, but I cannot find a way to resume an existing ~/.claude/projects/**/*.jsonl session from the app. I also tried /desktop, but it is not recognized in Claude Code 2.1.216.

Environment

  • macOS
  • Claude Code: 2.1.216
  • Claude App: /Applications/Claude.app
  • Existing target session:
  • session name: copilot-search
  • started with: claude --resume copilot-search

Expected behavior

There should be a clear way to continue an existing local Claude Code session in Claude App Code, instead of starting a fresh blank Code session.

For example, one of these would be enough:

  • select or search a local historical session inside Claude App Code
  • run a Claude Code slash command that registers the current session with the app
  • start claude --resume ... with an official flag and then take over from Claude App

Actual behavior

Claude App Code shows local stats and project context:

  • Sessions: 157
  • Messages: 92,145
  • local folder chips such as Learn, devonthink, skill, and remote

However, these folders appear to be new-task context chips, not a historical session list. Clicking the relevant project folder did not open the existing copilot-search session.

What I tried

/desktop

I resumed an existing session in a real Claude Code TUI and typed:

/desktop

Result:

Unknown command: /desktop

So /desktop does not appear to be available in Claude Code 2.1.216.

/remote-control

In the same Claude Code TUI, I typed:

/remote-control test-cv

Result:

/remote-control is available with Claude for Enterprise — ask your admin about migrating from API-key access.

doctor

claude --setting-sources local doctor reports:

Remote Control requires a claude.ai subscription. Run claude auth login to sign in with your claude.ai account.
- Not signed in to claude.ai
- claude.ai subscription auth not active
- Sign-in is missing the user:profile scope
- Org policy does not allow Remote Control (allow_remote_control)

claude --setting-sources local auth status reports:

{
  "loggedIn": true,
  "authMethod": "claude.ai",
  "apiProvider": "firstParty",
  "apiKeySource": "/login managed key",
  "subscriptionType": null
}

Questions

  1. Does Claude App Code support resuming existing local Claude Code sessions from ~/.claude/projects/**/*.jsonl?
  2. If yes, where is the entry point: App UI, slash command, or CLI flag?
  3. Has /desktop been removed or renamed? If so, what is the current replacement?
  4. If /remote-control is the only supported path, is Claude for Enterprise required, or is there another path for regular local Claude App users to continue an existing session?

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗