Control Claude Code from your phone, then let it work without you

What is Claude Code Remote Control?

Remote Control connects claude.ai/code and the Claude app for iOS and Android to a Claude Code session running on your machine. Claude keeps running locally the whole time; your phone or browser is a window into that session.

• Your files, MCP servers, tools and project settings stay available, because nothing moves to the cloud.
• The conversation stays in sync, so you can type from the terminal, a browser and your phone interchangeably.
• You can send photos and files from your phone; Claude Code saves them on your machine.
• If your laptop sleeps or the network drops, the session reconnects when the machine is back online.

How to use Claude Code from your phone

1. Check your plan and sign-in

   Remote Control works on Claude Pro, Max, Ultra, Team and Enterprise plans, signed in through claude.ai with /login. API keys, Amazon Bedrock, Google Cloud, Microsoft Foundry and custom ANTHROPIC_BASE_URL gateways aren't supported. On Team and Enterprise an Owner turns it on first.

2. Start a session with Remote Control on

   Start a new interactive session with the flag, or turn it on in a session that's already running. The VS Code extension and the Claude desktop app take the same /remote-control command.

   claude --remote-control "My project"
   # or, inside a running session
   /remote-control

3. Open it on your phone

   Scan the QR code Claude Code shows in the terminal, or open the session from the list at claude.ai/code or in the Claude app. Run /remote-control again to see the link, the QR code or to disconnect.

4. Keep your computer on

   The session runs on your machine, so the computer has to stay on and the claude process has to keep running. Close the terminal and the remote session ends with it.

Source: Anthropic's Remote Control documentation

What Remote Control doesn't do

Remote Control is a remote screen for a conversation. It doesn't decide what Claude should do next, so the work still moves only when you do.

• Claude acts when you send a message. When a task is done, it waits for you.
• There's no list of tasks, owners or statuses: each session is one conversation.
• It doesn't know your goals or working hours, and nothing wakes it up on a schedule.
• Running several Claude Code agents means juggling several sessions yourself.

Remote Control vs. Crewmark

Give Claude Code a job, not just a remote

Crewmark makes the Claude Code on your machine an employee: it has a role, goals, working hours and a board of issues, and it keeps working on them whether or not you're watching.

1. Hire an employee

   Pick a role such as SEO specialist or software engineer, write its goals and KPIs, and set its working hours and heartbeat.

2. Connect a Claude Code conversation

   Paste the setup link into Claude Code. It installs the crewmark CLI and links that conversation to the employee. Codex works too.

3. Assign issues from any browser

   Create issues on the board from your phone or laptop and assign them. The employee hears about them right away.

4. It works on a heartbeat

   During working hours the employee is woken on a schedule, picks up its issues, updates their status and comments on its progress. When it needs a decision, it asks you.

Use both

A Crewmark employee is an ordinary Claude Code conversation, so you can still turn on Remote Control for it and jump in from your phone. Remote Control lets you talk to Claude Code from anywhere; Crewmark gives it something to do while you're not talking.

Questions