[FEATURE] Mobile companion app to control Claude Code sessions remotely

Resolved 💬 2 comments Opened May 11, 2026 by yramstech 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

Claude Code currently requires the developer to be physically at their PC to:

  • Respond to AskUserQuestion prompts
  • Approve or decline tool/permission requests
  • Provide follow-up instructions when Claude pauses for clarification

This means long-running tasks (large refactors, multi-file edits, deep investigations) effectively chain the developer to their desk. One missed prompt during a coffee break, meeting, or commute stalls the entire session.

Proposed Solution

A lightweight mobile app that connects to Claude Code on the user's PC, with three core capabilities:

1. PC-to-mobile pairing

Secure pairing between the mobile app and Claude Code running locally — e.g. via one-time code or QR scan. iOS and Android.

2. Live view of active tasks

The mobile app shows all currently running Claude Code tasks on the paired PC:

  • Current step / what Claude is working on
  • Files being modified
  • Status: actively working vs. waiting for user input

3. Remote response to prompts

When Claude triggers an AskUserQuestion or requests permission for a tool action:

  • User receives a push notification on mobile
  • User can read the full context in the app
  • User can accept, decline, or send a custom instruction directly from their phone

Use Cases

  • Kick off a large refactor before leaving the house, approve intermediate steps from the train
  • Run an overnight investigation task and respond to clarifying questions in the morning without losing hours
  • Start a multi-file generation, step into a meeting, keep the task moving from the phone
  • Solo founders and small teams: stop being the single point of failure that blocks every long-running agent task

Why This Matters for Claude Code Specifically

Claude Code is moving toward more autonomous, agentic workflows. The main bottleneck preventing true async usage today is the human-in-the-loop requirement at the PC. A mobile companion keeps the human in the loop but removes the physical tether — exactly the constraint that limits how much real work Claude Code can complete per day.

Additional Notes

  • Authentication should be secure by default (paired devices only, revocable)
  • Could potentially leverage the existing Claude mobile app rather than shipping a separate one

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

Interactive mode (TUI)

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 ↗