Claude Code remote control: phone and browser options

To control Claude Code remotely, run claude remote-control in your project, or type /remote-control in a session that is already open, then open that session at claude.ai/code or in the Code tab of the Claude app on your phone. The session keeps running on your computer, so the computer has to stay on with Claude Code running. VibeiDE adds its own phone control for a different job: queueing and reviewing many Claude Code and Codex tasks across projects.

14-day trial. No card. Provider costs are separate.

How do I start Claude Code Remote Control?

Use one of three commands. Run claude remote-control in your project folder to start a server that waits for remote connections. Run claude --remote-control, or --rc, for a normal interactive session that you can also reach remotely. Or type /remote-control, or /rc, in a session that is already open; it carries the current conversation over. The first run asks you to confirm that you want Remote Control on. Sign in with /login first, because API keys are not supported.

How do I connect from my phone or a browser?

The terminal shows a session URL that opens in any browser at claude.ai/code. In server mode, press the spacebar to show a QR code and scan it to open the session in the Claude app for iOS or Android. You can also open the app, tap Code and pick the session by name; a session that is online shows a computer icon with a green dot. Sign in with the same claude.ai account you use for Claude Code. If you do not have the app yet, /mobile shows a QR code that leads to the right app store.

What Remote Control gives you

As of November 2026, Remote Control is a window into a session that keeps running on your computer. Your files, MCP servers, tools and project configuration stay local, and the conversation stays in sync between the terminal, the browser and the phone, so you can type from any of them. You can attach photos and files from the phone, see a diff of your changes, and get push notifications when a long task finishes or Claude needs a decision. Turn those on in /config with Push when Claude decides and Push when actions required.

Where Remote Control stops

Remote Control is available on Pro, Max, Team and Enterprise plans, and on Team and Enterprise an Owner has to enable it first. The computer has to stay on and the claude process has to keep running: close the terminal and the session goes offline. Outside server mode, each Claude Code process serves one remote session; server mode serves several, 32 by default. Commands such as /plugin and /resume work only in the terminal, and Bypass permissions cannot be selected from the app. While connected, the session transcript is stored on Anthropic servers.

When the computer will be off

Anthropic’s docs point to cloud sessions for that case. You start one from the Code tab of the Claude app by choosing a GitHub repository and a branch and describing the task; it runs on cloud infrastructure and continues after you put the phone away. Dispatch, on Pro and Max plans, lets you message a task to the Claude Desktop app on your computer. Both are Anthropic features and work without VibeiDE.

Where VibeiDE phone control fits

VibeiDE is a desktop app that queues tasks for the Claude Code, Codex and OpenCode CLIs you already have. Its Mobile control is a separate feature, not a wrapper around Remote Control: the phone talks to VibeiDE on your computer instead of to one Claude Code conversation. From the phone you queue a task into a project, send a follow-up, answer a question an agent is waiting on, read the result and mark the task reviewed, across every project you chose to share. The work still runs on your computer, so it has to stay awake with VibeiDE open.

How to pair a phone with VibeiDE

In VibeiDE, open Connect devices and choose Mobile control. Name the computer, pick the projects to share and select Create QR code. Scan the code with your phone, sign in to VibeiDE Mobile at remote.vibeide.dev/mobile/ and tap Connect computer. Both screens then show a six-digit code: check that they match and choose Codes match, enable on the computer. The phone app runs in the browser and can be added to your home screen. Mobile control needs an account with a verified email and two-factor authentication.

How the connection is protected

Pairing gives the phone its own keys, and the computer accepts commands only from phones it enrolled itself. Commands and results are end-to-end encrypted between that phone and the computer, and each command is signed. The hosted relay passes sealed messages on; it sees routing metadata, timing and sizes, not content. Work started from a phone uses the Restricted profile by default: Claude Code edits files only, and anything else waits for you at the computer. Notifications never include prompts or results.

Which one should I use?

Use Remote Control when you want to keep steering one Claude Code conversation that you started at your desk. Use a cloud session when the computer will be off. Use VibeiDE when the work is many separate tasks across several projects, with Claude Code and Codex side by side, and you want each result to wait in Ready for review until you have looked at it. VibeiDE runs on macOS, Windows and Linux and has a 14-day trial with no card.

Sources: Claude Code Remote Control, Claude Code on mobile.

Related guides

All articles

Necessary cookies support sign-in, security, your language and this choice. Optional categories stay off until accepted.

First-party page views and acquisition measurement, plus Google Analytics 4 (Google Ireland, data may reach the US). Advertising personalization stays off.

With Analytics enabled, retain Google, Microsoft and Reddit ad click identifiers and share download, signup, activation and purchase conversions with the relevant ad provider. No personalized advertising.

Privacy · Cookie inventory