Control 1DevTool From Your Phone

Use Remote Control over your LAN, a Cloudflare tunnel, or Tailscale to run agents, review diffs, approve plans, and watch your teams — from your phone.

Remote Control turns your phone into a window onto the machine where 1DevTool is running. Kick off an agent from the couch, review a diff on the train, or reply to a prompt that's been waiting for your input — without opening your laptop. Everything runs on your own machine; your phone is just the remote.

1DevTool Remote Control project list on a phone

Turning It On

  1. On the desktop, open Remote Control from the status bar and enable it.
  2. 1DevTool generates a private URL and a QR code. Scan the code with your phone, or open the URL in your mobile browser.
  3. Sign in when prompted. The connection stays tied to your machine — only you can reach it.

Three connection modes

  • Local Network — the phone and the desktop are on the same Wi-Fi.
  • Cloudflare Tunnel — a secure Cloudflare tunnel, so you expose no ports and set up no VPN.
  • Tailscale / VPN — your phone reaches the desktop over your own tailnet.

Tailscale is worth the setup if you have it: nothing is exposed to the public internet, there is no tunnel warm-up wait, and full iOS Safari works, so you are not pushed into the in-app scanner browser on a home network. The panel tells you plainly whether Tailscale is installed, running, and connected, and switches the QR code and pairing URL to the tailnet address. When your tailnet needs HTTPS enabled, a guided one-time step does it.

Start on Launch

Turn on Start on Launch in Settings → Remote and the remote server starts every time 1DevTool opens, so a paired phone reconnects on its own after a restart or an update. A badge next to the switch shows the mode it starts in.

  • Local Network — the server comes up on your Wi-Fi as soon as the app opens.
  • Tailscale — if Tailscale is still connecting after a reboot, 1DevTool waits up to two minutes for it and serves on your local network meanwhile.
  • Cloudflare Tunnel is public, so it never starts by itself. The switch is turned off while that mode is selected; pick Local Network or Tailscale to use it.

Settings, Remote with Tailscale / VPN selected and the Start on Launch switch turned on

The phone app

Get the app. On iPhone and iPad, install 1DevTool from the App Store. It's free and needs iOS 17 or later. On Android, install 1DevTool from Google Play. It's free too and needs Android 8.0 or later.

Settings → Remote has two tabs: Web UI, which is everything on this page, and Phone, which still shows a Beta tag. The Phone tab hosts the 1DevTool mobile app. The host is off by default. Once you switch it on, it listens on the Remote Control port over your local network or your Tailscale tailnet. The link is end-to-end encrypted, and no relay or tunnel is involved. The Cloudflare tunnel is only for the browser client.

The Phone tab also links to a setup guide, Read how to install and use the 1DevTool mobile app beta →, which you can also read here. It was written for the beta, so on iPhone install from the App Store instead of TestFlight, and on Android install from Google Play instead of asking for an invite. The rest of its setup steps still apply.

The section lists the addresses a phone can reach and shows a Pairing code that expires in ten minutes, with Copy code and New code. In the app, choose Add computer and scan the code. The phone pairs as Viewer, and 1DevTool then asks you which role it gets (Viewer, Approver, Operator or Admin). Typing into terminals needs Operator. Each code pairs one phone and stops working after five failed attempts. One address can make 20 pairing attempts a minute, and up to 32 phones can be paired. Paired phones are listed with their platform and when they were last seen, and you can rename one, change its role, or Forget it, which ends its live session.

Pairing is single-use and read-only first

  • A QR invite works once and expires after ten minutes. Scanning it consumes the code and a fresh one replaces it, so a photographed or stale code cannot be replayed. The pairing reply itself travels encrypted.
  • A new phone connects as a Viewer unless you have chosen otherwise. It can read this desktop's workspace, including files and transcripts, but actions need a broader role — see Permissions below.
  • The role for QR pairings can be remembered. When a device scans the QR code, tick Don’t ask again in the role dialog, or set New QR Devices in Settings → Remote to Ask every time or a fixed role. Choosing any role above Viewer still asks you to confirm first. Passcode sign-ins always ask.

How long a phone stays paired

Settings → Remote → Pairing Expiry offers 7 days, 30 days or 90 days max. There are no unlimited credentials any more.

Browser pairings expire at most 7 days after pairing, whichever option you pick, and activity never renews them. Using the phone every day does not extend its access; when the week is up, pair again. Changing the setting can shorten an existing pairing, never lengthen it.

On an HTTPS Remote URL the browser keeps its half of the pairing in protected storage as a non-extractable key, so a script reading the page's storage cannot walk off with it. Over plain HTTP the pairing lasts only for that tab — reloading needs a fresh pairing — so prefer the HTTPS URL.

Once connected, your projects appear on the phone exactly as they're organized on the desktop. Tap one to drop into its workspace.

What You Can Do From Your Phone

Remote Control mirrors the parts of 1DevTool that matter when you're away from the keyboard.

Prompt and steer your AI agents

Open any project's terminal, read the agent's latest output, and send a new prompt — including agents that have been sitting idle waiting for your go-ahead. You can:

  • Scroll and copy terminal text in a mobile-friendly reader mode
  • Attach an image from your phone straight into the prompt
  • Mention a file in the repo so the agent has the right context
  • Reuse a past prompt from your prompt history

Prompt history on the phone

Review code and ship with Git

Browse the project's files, open a commit's details, and review diffs on your phone. When a change looks good, stage it, write a message, and push — a full source-control loop from the palm of your hand.

File viewer and Git control in Remote Control

Test APIs and query databases

Send an HTTP request and inspect the response, or run a database query, using the same collections and connections you've set up on the desktop. Requests you save stay in sync between phone and desktop.

Running a database query from Remote Control

Schedule a prompt for later

Queue an Agent Input prompt to fire on a timer, at a specific time, or at the next quota reset — so a long task can start while you're away and be ready when you get back.

Scheduling an Agent Input prompt with a timer

Read the transcript properly

Reader Mode re-renders an agent's conversation as a document, which is what makes catching up from a phone bearable. User messages, agent results, code, and raw terminal output are styled separately, with light, sepia, and dark reading surfaces and a default that follows your device theme.

Reader Mode on the phone

Terminals sized for your screen

Open a terminal on your phone and it reflows to fit: the phone that is actively looking at a terminal owns its width, so lines wrap for your screen instead of forcing you to pan across a desktop-width grid. The newest output and the agent's input box sit where you can see them.

Two phones viewing at once settle on a size that works for both, and the moment you close the terminal the desktop pane gets its own size back. While a phone is attached, the desktop pane says so with a Sized for phone badge and a shortcut into Reader Mode. Read-only viewers keep the previous mirrored view.

This works the same for a terminal that runs on a paired computer. Open it through the Host picker and it fits your phone's width; A− and A+ in the text size bar change its columns, and that computer's pane shows Sized for phone · <phone> via <computer> while your phone holds the width. When you leave the terminal, it goes back to its desktop size. If the paired computer runs an older 1DevTool, or your access is view-only, the terminal keeps that computer's width and the text size panel says why, with Open Reader as the way to read full lines.

Approve a plan from the kitchen

Tasks waiting on your verdict get their own page. Read the plan, then Approve or Request changes — your words travel to the agent verbatim, and nothing auto-approves while you are away. See Approval Gates.

See your whole team on a map

The Maps tab (next to Agents, Projects and Inbox) draws each project as a live map: every agent terminal is a desk, every link between two agents is a line, and the layout follows the chain of command. An org chart keeps its tiers, a team's host sits above its members, and agents with no links wait in a Not linked list under the map.

  • Pick a project from the chips under Maps — Live terminals & links. A summary line reads like 4 agents · 3 links · 4-seat org, and names any vacant seats.
  • Read the desks. Each shows its role and state, such as devin · running. A desk that is waiting on you (its AI run just finished, or a team member was flagged as needing input) is marked, and the header counts them: 3 needs you.
  • Read the lines. A solid line is a live link, a dashed line is a quarantined link (suspended because its terminal closed or relaunched, its session was replaced, or its agent or worktree changed). A straight line carries messages both ways, a curved one only one way.
  • Tap a desk to open that terminal on the phone.
  • When a link request is waiting, a banner reads 1 link decision waiting — answer in Inbox.

The team, hierarchy and run views that used to have their own Team tab are under Teams, runs & logs in the Start list below the map. See Team Map for the desktop version of the same picture.

Three phone screens: the Orchestrate Agents sheet with saved charts and Start team buttons, a live Maps view of four linked agent desks, and the same map flagging three agents that need you

Start a saved team

The org charts and pipelines you saved in the desktop Builder can be started from the phone. Open a project's Orchestrate Agents sheet, pick Add Terminal → Orchestration, or tap Start a team from a chart on the Maps tab.

Each chart is a card showing its roles or stages and how many terminals it opens (opens 4). Preview draws it the way the Builder does, with role cards and reporting lines for an org chart and numbered stages for a pipeline. Start team opens every seat as a fresh terminal, already linked by the chart, and counts Opening 2/4 terminals… while it works.

  • From the phone every seat opens a new terminal. Handing a seat to a terminal that is already open is desktop-only.
  • A chart with live seats is not replaced. If that chart is already running in the project, the button stands down and names it; stop or replace it from the desktop.
  • Starting a team needs Operator access on that device.

No saved chart fits? Plan a team from a goal has a planner propose the members, and nothing runs until you approve.

Start an agent on a paired computer

Pick a paired computer in the phone's Host picker, open a project there and choose Add Terminal. The sheet offers only the AI agents detected on that computer, and Start on followed by the computer's name starts one. This needs Operator or Admin access on the phone and the Start terminals grant on the paired computer.

When an agent there stops on a first-run question, the phone names it and answers it with one tap:

AgentQuestionButton
CodexTrust this folderTrust folder
CodexUpdate before startingSkip update
Cursor AgentTrust this workspaceTrust workspace
OpenCodeUpdate before startingSkip update
DevinTrust the authors of this folderTrust folder

Steer conversations between computers

Conversations between agents on two computers appear in the Inbox. Approver, Operator and Admin devices can Pause conversation, Resume, End or Deliver now; a view-only device is told to pause or end on the desktop.

The Inbox tab lets you grant a link request or release a queued message from the phone, with permission chips so you can see what you are granting before you tap. Approver devices decide; view-only devices see the request and are told to confirm on the desktop. A link that asks for read access can only be denied from the phone, because approving it needs the desktop's disclosure review.

Watch a hierarchy from your phone

Teams, runs & logs shows each active org by level — host on top, members below, each desk lit by the agent's real state, with the same office look as the desktop — and marks vacancies and routing violations. Approver devices can rebind a seat with one tap. See Agent Hierarchy.

Read orchestration run logs

Browse recent runs, open a run's files, and read the app log without walking back to the desk.

Check your AI quota

An AI Quota section shows headroom per provider and per account, so you can tell whether a long run will survive the night before you start it. See Accounts & Quota.

Skills and slash commands

The skills picker is available on the phone too, so you can insert a skill or a slash command without typing its name from memory.

The skills picker on the phone

Notifications

Turn on activity notifications and your phone lets you know when an agent finishes, needs input, or a long-running command completes — so you don't have to keep the app open to know when to step back in.

An activity notification from Remote Control

Permissions

Every paired device has a role, set per device in Settings → Remote on the desktop:

RoleWhat it allows
ViewerRead the desktop's workspace, including files and transcripts. Every new pairing starts here, unless New QR Devices in Settings → Remote names another role for QR pairings.
ApproverApprove agent actions and task gates, which can have destructive consequences.
Operator / AdminBroad command execution and write access to this desktop workspace, including opening previews of a localhost port.

Raising a device above Viewer asks for confirmation on the desktop, naming the device and what it will be able to do. Lowering a device cuts its live connections straight away rather than letting them keep the old level, and a scheduled prompt re-checks the device's grant when it comes due. Devices paired before these roles existed were reset to Viewer — the desktop marks them so you can confirm any broader role deliberately.

Previews of a localhost port need Operator or Admin, and each one gets its own short-lived grant for that port instead of riding on the pairing. When it lapses the phone asks you to open the preview again.

A send the desktop cannot confirm is not retried blindly. If the phone cannot confirm a prompt reached the terminal, the composer warns Check terminal before resending, keeps your draft, and puts the raw error behind Details — so an innocent retry does not send the prompt twice.