iOS app doesn't discover remote-control sessions from Docker containers

Resolved 💬 3 comments Opened Mar 10, 2026 by anthonygunawan Closed Mar 10, 2026

Description

Remote control sessions started from Claude Code running inside a Docker container (Alpine Linux) are not discoverable by the Claude iOS app, but work fine when opened in a web browser on claude.ai.

Remote control sessions started from Claude Code running natively on macOS on the same machine, same account, same version are discoverable by the iOS app.

This is different from #28758 where remote control doesn't work on iOS at all — in this case, native sessions work fine, only container sessions are invisible to the iOS app.

Steps to Reproduce

  1. Run Claude Code natively on macOS, start /remote-control → iOS app discovers the session ✅
  2. Run Claude Code inside a Docker container (node:20-alpine), start claude remote-control → iOS app does not discover the session ❌
  3. Open the container's session URL in a web browser → works fine ✅

Environment

  • Claude Code version: 2.1.72 (identical in both host and container)
  • Host OS: macOS (Darwin 25.3.0)
  • Container: Alpine Linux (node:20-alpine), Docker Desktop
  • Same OAuth account, same anonymousId, same userID in both .claude.json files
  • Auth tokens are copied from host to container at startup

Analysis

Since the web version works with direct URL navigation but the iOS app can't discover the container session, the issue likely involves platform/environment metadata sent during remote control session registration. The iOS app's session discovery API may be filtering based on OS or environment metadata, excluding sessions originating from Linux/Docker containers.

Related

  • #28758 — general remote control not connecting from mobile app

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗