iOS app clones repo instead of connecting to remote control server
Resolved 💬 3 comments Opened Apr 16, 2026 by joeshull Closed Apr 20, 2026
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
- Set up a remote control server on a Linux host:
````
claude remote-control --permission-mode bypassPermissions --name "my-server"
- Server logs confirm correct mode: "New sessions will be created in the current directory"
- Open the Claude iOS app and select the remote server
- Instead of connecting to the working directory, the app shows
git@github.com:...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.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗