claude-code - 💡(How to fix) Fix iOS app clones repo instead of connecting to remote control server [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#49126Fetched 2026-04-17 08:50:10
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Timeline (top)
labeled ×3commented ×1

When selecting a remote control server in the iOS app, sessions now attempt to clone the git remote URL instead of connecting to the remote server's working directory. This previously worked correctly — sessions would land in the server's working directory.

Root Cause

When selecting a remote control server in the iOS app, sessions now attempt to clone the git remote URL instead of connecting to the remote server's working directory. This previously worked correctly — sessions would land in the server's working directory.

Fix Action

Fix / Workaround

  • This also reproduces on servers with no git repo at all — the app still does not connect properly.
  • The server-side spawn mode is correct ("current directory", not clone mode).
  • Claude Code CLI version: 2.1.110
  • Server OS: Linux (Ubuntu)
  • The web client and desktop app are not available as workarounds in this user's environment.

Code Example

claude remote-control --permission-mode bypassPermissions --name "my-server"
RAW_BUFFERClick to expand / collapse

Description

When selecting a remote control server in the iOS app, sessions now attempt to clone the git remote URL instead of connecting to the remote server's working directory. This previously worked correctly — sessions would land in the server's working directory.

Steps to reproduce

  1. Set up a remote control server on a Linux host:
    claude remote-control --permission-mode bypassPermissions --name "my-server"
  2. Server logs confirm correct mode: "New sessions will be created in the current directory"
  3. Open the Claude iOS app and select the remote server
  4. Instead of connecting to the working directory, the app shows [email protected]:... and attempts to clone the repo

Expected behavior

iOS app connects to the remote server and opens a session in the server's working directory (previous behavior).

Actual behavior

iOS app interprets the git remote URL metadata as a clone instruction and attempts to set up a cloud sandbox with a git clone.

Additional context

  • This also reproduces on servers with no git repo at all — the app still does not connect properly.
  • The server-side spawn mode is correct ("current directory", not clone mode).
  • Claude Code CLI version: 2.1.110
  • Server OS: Linux (Ubuntu)
  • The web client and desktop app are not available as workarounds in this user's environment.

extent analysis

TL;DR

The iOS app may need a configuration change or update to correctly interpret the remote control server's working directory instead of attempting to clone a git repository.

Guidance

  • Verify that the claude remote-control command is correctly setting the permission mode and server name, and that the server logs confirm the expected behavior.
  • Check the Claude Code CLI version (2.1.110) for any known issues or updates that may address this problem.
  • Investigate the iOS app's configuration and settings to see if there are any options or flags that can be set to disable the git clone behavior and connect to the remote server's working directory instead.
  • Test the connection with a different remote control server or a different client (if available) to isolate the issue.

Example

No code snippet is provided as the issue seems to be related to the app's behavior and configuration rather than a specific code error.

Notes

The issue may be specific to the iOS app and the Claude Code CLI version being used. The fact that the web client and desktop app are not available as workarounds limits the options for testing and troubleshooting.

Recommendation

Apply a workaround, as the issue seems to be related to the app's behavior and configuration, and there is no clear indication of a fixed version available. The reason is that the issue is likely related to the app's interpretation of the remote control server's metadata, and a workaround may be necessary to bypass this behavior.

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…

FAQ

Expected behavior

iOS app connects to the remote server and opens a session in the server's working directory (previous behavior).

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix iOS app clones repo instead of connecting to remote control server [1 comments, 2 participants]