claude-code - 💡(How to fix) Fix Remote control sessions from VPS don't persist in desktop app history [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46335Fetched 2026-04-11 06:23:00
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×3commented ×1

Remote control sessions bridged from a VPS (Hetzner, Ubuntu 24.04) do not persist in the Mac desktop app's session history after disconnecting. Sessions from a local machine (Dell) persist correctly.

Root Cause

Remote control sessions bridged from a VPS (Hetzner, Ubuntu 24.04) do not persist in the Mac desktop app's session history after disconnecting. Sessions from a local machine (Dell) persist correctly.

Fix Action

Workaround

Currently saving full session transcripts to the git repo manually as a workaround.

RAW_BUFFERClick to expand / collapse

Description

Remote control sessions bridged from a VPS (Hetzner, Ubuntu 24.04) do not persist in the Mac desktop app's session history after disconnecting. Sessions from a local machine (Dell) persist correctly.

Steps to Reproduce

  1. Set up Claude Code on a remote VPS (Ubuntu 24.04, running as a non-root claude user)
  2. Start a session: claude --remote-control-session-name-prefix VPS --dangerously-skip-permissions
  3. From the Mac desktop app, connect via /remote-control VPS
  4. Session appears in the left sidebar while connected — works fine
  5. Interact normally, then disconnect / close the session
  6. Session disappears from the "All projects" sidebar history — no way to access it again from the Mac app

Expected Behavior

Bridged remote control sessions should persist in the Mac app's session history after disconnecting, same as sessions from other remote machines.

Actual Behavior

  • VPS remote sessions: Visible while live, disappear from sidebar history after disconnect
  • Local machine (Dell) remote sessions: Persist in history permanently (correct behavior)

Both use the same Mac desktop app and the same account.

Environment

  • Client: Claude Code Mac desktop app, Max plan
  • Server: Hetzner CX33, Ubuntu 24.04, Claude Code 2.1.100
  • Server user: claude (non-root, UID 1000)
  • Auth: OAuth
  • Launch command: claude --remote-control-session-name-prefix VPS --dangerously-skip-permissions

Workaround

Currently saving full session transcripts to the git repo manually as a workaround.

extent analysis

TL;DR

The issue with remote control sessions not persisting in the Mac desktop app's session history after disconnecting from a VPS may be resolved by investigating the differences in configuration or environment between the VPS and local machine setups.

Guidance

  • Verify that the claude user on the VPS has the necessary permissions to write session history data, as the --dangerously-skip-permissions flag may be masking underlying issues.
  • Compare the launch commands and configurations used for the local machine (Dell) and VPS setups to identify any discrepancies that could be causing the session history persistence issue.
  • Check the OAuth authentication settings to ensure that they are correctly configured for both the local machine and VPS setups.
  • Investigate the possibility of a version mismatch or compatibility issue between the Claude Code Mac desktop app and the Claude Code server version (2.1.100) on the VPS.

Example

No specific code example is provided, as the issue seems to be related to configuration and environment rather than code.

Notes

The provided workaround of saving full session transcripts to the git repo manually may be useful for preserving session data, but it does not address the underlying issue of session history persistence.

Recommendation

Apply a workaround by reconfiguring the VPS setup to match the local machine setup as closely as possible, and then test to see if the issue persists. This approach may help identify the root cause of the problem and provide a temporary solution until a more permanent fix can be found.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING