[FEATURE]

Resolved 💬 3 comments Opened Feb 28, 2026 by kenneth-copeland Closed Mar 4, 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

continue working with my existing claude code session using remote-control with voice input/output similar to Perpexity app on both Android and IOS

Proposed Solution

I want to work with Claude Code at my desk all morning, then take my dog for a walk and continue interacting with my session by voice from my phone — talking to Claude, hearing its responses, and steering it hands-free while it works on my codebase back home.
Basically the same conversational voice flow that Perplexity has on mobile, but connected to my live Claude Code session.
What's missing today

The Android Claude app doesn't show a Code tab or list available Remote Control sessions. The only way I can connect is by emailing myself the session URL and opening it in a browser.
The browser experience at claude.ai/code has no voice/audio support, so I'm stuck typing on a tiny screen.
Claude Code output is extremely verbose (full file contents, diffs, tool outputs), making it nearly unreadable on a phone screen.
The Claude app already has voice. Claude Code already has Remote Control. They just aren't wired together yet.

What would make this work

Android app needs a working Code tab that shows active Remote Control sessions (like iOS reportedly has).
Voice input/output support for Remote Control sessions in the mobile app — talk to Claude, hear responses back.
A mobile-optimized view that summarizes output instead of dumping raw terminal content. On a phone I don't need to see every line of a diff — I need Claude to tell me what it did and ask me what's next.
Smarter voice activation — automatic voice mode like Perplexity, but with much better noise filtering. Perplexity's voice mode is way too sensitive to ambient noise and stops talking at the slightest sound in the room. Claude should be more robust here — don't cut off audio output because a dog barked or a door closed.
Proper audio output device selection on Android — route audio output to the correct user-selected output device. Currently neither Claude nor Perplexity properly respect the selected audio output stream on Android. If I have Bluetooth earbuds connected or a specific output device selected, the audio should go there without fighting me.

Environment

Claude Code v2.1.63
Max plan
Android phone
Remote Control starts fine on desktop, but mobile experience is not usable yet

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

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