Feature Request: Claude Code Mobile Companion — Remote Session Control & Voice Input

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's agentic workflows are powerful but not fully autonomous. Agents periodically pause for input: permission to proceed, a choice between approaches, or a small clarification. Today, if you step away from your laptop — to the gym, on a hike, running errands — your agents sit idle until you return. The bottleneck isn't compute or intelligence. It's physical proximity to a keyboard.

This creates a frustrating gap: Claude Code can work for hours on your behalf, but a 10-second approval can block it for hours if you're not at your desk.

User Story:

I'm running Claude Code on my laptop with multiple agents refactoring a large codebase. I head to the gym. Fifteen minutes in, I get a notification on my phone: "Agent needs approval — proposing to restructure the database schema. Review changes?" I glance at the diff summary, tap "Approve with note," and dictate: "Looks good, but keep the existing column names for backward compatibility." The agent continues. I finish my workout. By the time I'm home, the refactor is done.

Proposed Solution

A mobile interface (tab within the Claude mobile app, or a standalone lightweight companion) that connects to active Claude Code sessions running on your machine. Two core capabilities:

1. Remote Session Monitoring & Approval

• Live session feed: See what your agents are working on, their current status, and any pending requests for input.
• Quick actions: Approve, reject, or redirect with a tap. Pre-built response options like "Yes, proceed," "Try a different approach," or "Skip this for now."
• Diff review: View proposed code changes in a mobile-friendly format. Approve or request modifications.
• Push notifications: Get alerted when an agent is blocked and needs input, so you don't have to keep checking.

2. Voice-Driven Instructions

• Voice input for directions: Dictate high-level instructions like "Focus on the authentication module next," "That approach looks good, go ahead," or "Revert the last change and try using the existing utility function instead."
• Conversational interaction: Have a back-and-forth with your agents via voice — review what they've done, ask questions about their approach, give guidance — all while walking, hiking, or commuting.
• Transcription + confirmation: Show a text preview of the transcribed instruction before sending, so nothing gets lost in translation.

Why This Matters

• Eliminates idle time: Agents keep moving even when the developer is away from their desk. A 10-second voice note replaces a 3-hour wait.
• Matches real workflow patterns: Developers think about their code constantly — in the shower, at the gym, on walks. Right now there's no way to act on those thoughts without getting back to a laptop.
• Plays to Claude Code's strength: The more autonomous the agents become, the more the human role shifts from writing code to providing direction. Direction doesn't require a keyboard — it requires a channel.
• Voice is natural for high-level guidance: The kind of input agents typically need ("yes proceed," "try X instead," "prioritize Y") is conversational, not syntactic. Voice is a perfect fit.

Technical Considerations

• Secure connection: Sessions could be linked via authenticated tunnel, QR code pairing, or through the user's Anthropic account as a bridge.
• Lightweight by design: The mobile interface doesn't need to be a full IDE. It's a control panel — status, notifications, quick input, voice. Keep it minimal and fast.
• Offline resilience: Queue instructions if connectivity drops and deliver them when reconnected.

Closing Thought

Claude Code is moving toward a world where AI agents build software while developers provide vision and judgment. That kind of oversight doesn't require sitting at a desk — it requires a communication channel. A mobile companion makes Claude Code truly asynchronous: your agents work while you live your life, and you stay in the loop with a glance and a sentence.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

Example scenario:

1. I'm running Claude Code on my laptop with 3 agents refactoring a large codebase — one handling database migrations, one updating API endpoints, and one refactoring the frontend components.
2. I leave my desk to go to the gym. Five minutes into my workout, I get a push notification: "Agent 1 needs approval — proposing to restructure the database schema. Review changes?"
3. I open the mobile companion on my phone, glance at the diff summary showing the proposed schema changes, and tap "Approve with note."
4. I dictate via voice: "Looks good, but keep the existing column names for backward compatibility."
5. The agent receives my instruction and continues working. Meanwhile, Agent 2 asks for clarification on an API naming convention. I tap a quick-reply: "Follow the existing pattern."
6. I finish my workout and head home. By the time I open my laptop, all three agents have completed their work — what would have been a 3-hour idle wait was reduced to two 10-second interactions on my phone.
7. This would save me hours of blocked agent time every week and let me stay productive even when away from my desk.

Additional Context

_No response_