Remote Control requires upfront planning; can't enable mid-session without losing work

Resolved 💬 2 comments Opened Jun 16, 2026 by cdwf01-code Closed Jun 20, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Remote Control creates a new independent session each time claude remote-control is invoked. There's no way to attach Remote Control to an already-running local session mid-way through.

This forces users to choose: either start every session with Remote Control enabled (in case they might need mobile access later), or accept that they can't access an in-progress session from Android/tablet without losing their work and starting fresh.

Current workaround: Start all sessions with claude remote-control preemptively, even if mobile access isn't needed.

Proposed Solution

Users should be able to enable Remote Control on an existing session, or at minimum, have a way to continue a local session via Remote Control without creating a new chat.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

API and model interactions

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

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