[FEATURE] Claude Code Mobile Companion App
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 runs exclusively in a desktop terminal environment. When I step away from my computer while Claude is working on a task, I have no way to:
- See if Claude is waiting for my input
- Check progress on longer tasks
- Quickly approve or reject suggestions
- Continue a paused session
My workflow is delegation-based: I discuss a problem with Claude, make a decision, then let Claude work autonomously while I do other things. This works great when I'm at my desk, but the moment I leave, I'm completely disconnected.
Current workarounds are impractical:
- SSH apps on mobile require too much typing
- vscode.dev on a phone screen is cramped and clunky
- There's no notification system to alert me when Claude needs input
I don't need to write code on my phone. I need to monitor and interact with Claude Code sessions - approve, reject, continue, stop. That's it.
Proposed Solution
A lightweight "Claude Code Companion" mobile app for iOS/Android focused on three things:
1. Monitoring
- See active sessions and their current status (running/waiting/finished/error)
- View Claude's output in a scrollable, readable format
- Optionally expand to see changed files or details
2. Interaction
- Text input for natural language instructions
- Quick action buttons: Continue, Stop, Approve, Reject, Commit, Test
- Draggable divider to adjust output vs. input area ratio
3. Notifications
- Push notification when Claude needs input
- Push notification when a task completes
- Actionable notifications (respond without opening the app)
What this is NOT:
- Not a full IDE or code editor
- Not a file browser
- Not a replacement for the desktop experience
Ideal UI:
- Top: Scrollable output area showing Claude's responses
- Middle: Draggable divider
- Bottom: Text input + quick action buttons
- Status indicator showing session state
Alternative Solutions
_No response_
Priority
Medium - Would be very helpful
Feature Category
Interactive mode (TUI)
Use Case Example
Scenario: Delegating a refactoring task before leaving the house
- At my desktop, I start Claude Code and say: "Analyze the auth module and suggest security improvements."
- Claude begins analyzing. I need to leave for an appointment.
- On my commute, I get a push notification:
"Claude Code: Session 'my-project' needs input - Found 3 issues in auth module. Should I fix them?"
- I open the companion app and see Claude's full analysis:
- Issue 1: Password hashing uses MD5 (critical)
- Issue 2: No rate limiting on login
- Issue 3: Session tokens don't expire
- I tap the text input and type: "Fix #1 and #2, skip #3 for now"
- Claude continues working. I put my phone away.
- 10 minutes later, another notification:
"Claude Code: Changes ready. 2 files modified. Commit?"
- I tap [Approve] directly on the notification without opening the app.
- When I get home, the work is done and committed.
Time saved: Instead of waiting at my desk or coming back to a stalled session, I stayed productive and kept Claude moving - all from my phone with minimal interaction.
Additional Context
UI Mockup
Main View
┌─────────────────────────────────────┐
│ ● Claude Code [Session 1] │
├─────────────────────────────────────┤
│ │
│ Claude: I've analyzed the auth │
│ module. Found 3 issues: │
│ │
│ 1. Password hashing uses MD5 │
│ 2. No rate limiting on login │
│ 3. Session tokens don't expire │
│ │
│ Should I fix these? │
│ │
│ ▼ [Show changed files] │
│ │
├─────────────────════════════════════┤
│ │
│ > Fix #1 and #2, skip #3 │
│ │
│ [Send] │
├─────────────────────────────────────┤
│ [Continue] [Stop] [Approve] [Commit]│
└─────────────────────────────────────┘Notification
┌─────────────────────────────────────┐
│ 🔵 Claude Code │
│ Session needs input │
│ "Should I refactor auth.py or..." │
│ │
│ [View] [Continue] [Stop] │
└─────────────────────────────────────┘Similar Features in Other Tools
- GitHub Mobile - Review PRs, approve/reject, respond to comments on the go
- Slack Mobile - Conversation-first interface, actionable notifications
- Linear Mobile - Manage tasks and issues without full desktop experience
Technical Considerations
Connection Options:
- Relay server (like VS Code Tunnels) - works through NAT/firewalls
- Direct P2P via Tailscale/WireGuard - no relay needed
- Hybrid approach - direct when possible, relay as fallback
Required Changes to Claude Code CLI:
- Background daemon mode for persistent sessions
- WebSocket/API endpoint for remote control
- Push notification trigger integration
- Session state serialization for reconnection
Additional Ideas
- Gesture support: Swipe right to approve, swipe left to reject
- Voice input: For longer instructions when typing is inconvenient
- Home screen widget: Glanceable status ("Running task 3/5" or "Waiting for input")
- Watch app (future): Apple Watch / WearOS for notifications + quick actions only
---
tl;dr: Let me check on Claude and tell it "yes" or "no" from my phone. That's it. That's the feature.
Showing cached comments. Read the full discussion on GitHub ↗
9 Comments
Bump 😉 ... Constantly recurring situations. I am away from the computer (shopping, kitchen, etc.) and Claude Code asks me to confirm or check something. A "co-worker app" would make many things much easier and more efficient.
+1 to this! The "away from computer but Claude needs me" situation happens constantly - especially for operations that need approval but don't need deep thought (like confirming a DB read or checking a log file).
This is exactly what ForkOff was built for - mobile approvals for Claude Code workflows.
How it works:
npm i -g forkoffforkoff pairCheck it out:
npm: https://www.npmjs.com/package/forkoff
The key insight: most approvals don't need a full keyboard - just "yes/no" or reviewing 20 lines of code. Mobile is perfect for that. You can literally approve a database migration while making coffee or review a config change from your couch.
First 2000 users get lifetime Pro access (early adopter perk).
What's your most common "wish I had my laptop" approval scenario?
(Disclosure: I'm building ForkOff, so biased, but this exact use case - shopping/kitchen/away from desk - is why we built it.)
This is exactly the workflow I built claude-relay for — your comment "I don't need to write code on my phone. I need to monitor and interact with Claude Code sessions - approve, reject, continue, stop. That's it." is what convinced me to build it.
https://github.com/chadbyte/claude-relay
Run
npx claude-relayin your project directory, scan the QR code with your phone, and you get a full Claude Code session in your browser with push notifications.No global install, no pairing step, no sign-up. Free and open source. Your code never leaves your machine.
Hey! This is exactly what we just launched with ForkOff - open beta is live now.
What We Built
Mobile app for Claude Code with the exact features you described:
Technical Approach
We went with a relay-based architecture (similar to how GitHub mobile works):
Beta Access
Just launched: https://forkoff.app (TestFlight)
Why We Built This
Saw multiple threads here (including this one!) about the "rushing back to desk" problem. Also saw folks building DIY solutions with SSH/tmux/Telegram bots.
We built a purpose-built mobile app instead.
Feedback Welcome
Early stage - would love input from this community on what else should be prioritized!
---
Disclosure: I work on ForkOff. Built specifically for the Claude Code/OpenClaw ecosystem.
Hey! This is exactly what we just launched with ForkOff - open beta is live now.
What We Built
Mobile app for Claude Code with the exact features you described:
Technical Approach
We went with a relay-based architecture (similar to how GitHub mobile works):
Beta Access
Just launched: https://forkoff.app (TestFlight)
Why We Built This
Saw multiple threads here (including this one!) about the "rushing back to desk" problem. Also saw folks building DIY solutions with SSH/tmux/Telegram bots.
We built a purpose-built mobile app instead.
Feedback Welcome
Early stage - would love input from this community on what else should be prioritized!
---
Disclosure: I work on ForkOff. Built specifically for the Claude Code/OpenClaw ecosystem.
Hey! This is exactly what we just launched with ForkOff - open beta is live now.
What We Built
Mobile app for Claude Code with the exact features you described:
Technical Approach
We went with a relay-based architecture (similar to how GitHub mobile works):
Beta Access
Just launched: https://forkoff.app (TestFlight)
Why We Built This
Saw multiple threads here (including this one!) about the "rushing back to desk" problem. Also saw folks building DIY solutions with SSH/tmux/Telegram bots.
We built a purpose-built mobile app instead.
Feedback Welcome
Early stage - would love input from this community on what else should be prioritized!
---
Disclosure: I work on ForkOff. Built specifically for the Claude Code/OpenClaw ecosystem.
While waiting for the official mobile app, you can bridge the local
claudeCLI directly to a Telegram/Feishu bot using pikiclaw. It runs in your actual local workspace, supports long-running tasks, and streams responses to your phone. Give it a try:npx pikiclaw@latest.This is still the right framing for the workflow: it is not "write code on a phone", it is "keep a long-running local CLI session moving when the user is away from the desk".
For people whose Claude Code / Codex work already lives in
tmux, I built a small open-source workaround in this narrower shape: https://github.com/Snailflyer/faryoFaryo keeps the Claude Code / Codex CLI / shell process inside the same live
tmuxsession and exposes a browser/PWA workbench for output review, short replies, approval/interruption, and handoff back into the same desktop terminal. It is not a remote desktop, hosted IDE, or second chat history. Current best-supported path is Linux +tmux+ Claude Code/Codex CLI + Chrome/Android Chrome PWA.Disclosure: I maintain Faryo. Sharing here because the original issue's "I don't need to write code on my phone; I need to monitor and interact" requirement is exactly the boundary it targets.
+1 on this, with a specific angle worth calling out: it's not just that there's no
mobile companion app in general — even the existing web Routines feature
(claude.ai/code/routines) has zero presence in the mobile app beyond push
notifications.
Once a routine's notification is dismissed or missed, there is no way in-app to:
Current workaround is opening claude.ai/code/routines in a mobile browser — which
works, but defeats the point of having a native app. A "My Routines" list view (or
at minimum a persistent link back to each routine's thread from notification
history) would fix this.