Skip to content
BSWEN
Blog

How to use Claude Code remote control from your phone

Cowrie
Cowrie
Dev @ Bswen

Purpose

This post demonstrates how to control Claude Code from your phone while you’re away from your desk.

When I’m in meetings or walking around, I often need to monitor coding work but can’t stay at my terminal. I tried to search for mobile coding solutions, but most options require complex setups or don’t work with my existing workflow.

Environment

  • MacBook Pro (M1)
  • Claude Code CLI (latest version)
  • Claude mobile app (iOS)
  • iOS 17.4

The Problem

When I started a refactoring task using Claude Code:

cowrie@macbook:~/project$ claude "Refactor the authentication module to use dependency injection"

Claude began working on the task, but I had to attend a meeting. I couldn’t see what changes were being made or guide the work while away from my desk.

The Solution: Remote Control

Claude Code now supports remote control through the mobile app or web interface. Here’s how it works:

┌──────────────┐    ┌─────────────────┐    ┌──────────────┐
│  Desktop     │    │  Anthropic      │    │  Mobile      │
│  Session     │───→│  Servers       │───→│  Interface   │
│  (Local)     │    │  (Bridge)      │    │  (Remote)    │
└──────────────┘    └─────────────────┘    └──────────────┘

How to Set Up Remote Control

  1. Start a Claude Code session locally

    Terminal window
    cowrie@macbook:~/project$ claude "Refactor the authentication module"

    Keep this session running - don’t exit it.

  2. Connect from your phone

    • Open the Claude mobile app
    • Or navigate to claude.ai/code in browser
    • Log in with the same account

  3. Control the session remotely You’ll see your active session listed and can continue the conversation.

What I Tried

First, I tried to start a session and then immediately switch to my phone:

Terminal window
cowrie@macbook:~/project$ claude "Fix the authentication bug"

Then I went to my phone and looked for the session. It wasn’t there because I hadn’t waited for the session to sync.

Then I tried starting the session and keeping it running in the background while I moved to my phone. This worked - I could see the session and continue the conversation.

Best Practices

What Works

Start with clear context before going mobile I found that if I start a session with detailed context on desktop, I need less time on mobile to guide the work.

Use mobile for high-level guidance, not code writing Trying to write code on mobile is difficult. I use it to review outputs and approve changes.

Keep your machine awake I use caffeinate to prevent my Mac from sleeping while using remote control.

Terminal window
cowrie@macbook:~/project$ caffeinate -d

What Doesn’t Work

Don’t expect full code editing on mobile The mobile interface is optimized for conversation, not coding. When I tried to write detailed instructions, it was cumbersome.

Don’t exit your terminal session When I accidentally exited the terminal, the remote control connection was lost and I had to start over.

Real Example

Here’s what my workflow looks like:

Terminal window
# 1. Start session on desktop
cowrie@macbook:~/project$ claude "Refactor user service to use dependency injection"
Claude begins working...


# 2. Go to meeting with phone
# 3. Check session on mobile app
# I can see: "I've created the UserService interface..."
# 4. Guide from mobile: "Make sure to update all tests"
# 5. Return to desktop
cowrie@macbook:~/project$ # All changes are reflected locally

The Reason Behind the Design

Claude Code’s remote control works by keeping the local CLI as the source of truth. The mobile device is just a remote control interface. This is different from other mobile coding approaches that try to run code on the device itself.

This design choice means:

  • All file operations happen locally (faster, no network delays)
  • Full context is maintained (no state loss)
  • No security risks (mobile doesn’t access your files)

This approach is similar to SSH + tmux workflows, but with AI capabilities. In traditional remote setups, you control the terminal directly. With Claude Code, you control an AI that can understand natural language and make decisions.

Another similar concept is IDE cloud services like GitHub Codespaces, but they require full desktop-like interfaces. Claude Code’s approach is much lighter - it’s just a conversation interface.

Summary

In this post, I showed how to control Claude Code from your phone while maintaining productivity away from your desk. The key point is that local sessions remain the source of execution, while mobile devices act as remote conversation interfaces.

This approach works well for scenarios like meetings, walking around, or when you need to briefly step away from your desk but stay in control of your coding tasks.

Final Words + More Resources

My intention with this article was to help others share my knowledge and experience. If you want to contact me, you can contact by email: Email me

Here are also the most important links from this article along with some further resources that will help you in this scope:

Oh, and if you found these resources useful, don’t forget to support me by starring the repo on GitHub!

Comments

Tags: