Paired iPhone control for your own machine

Run your own computer from iPhone.

Pair a Mac or Linux host, run local Codex or Claude work by text or voice, and keep planning, execution, results, and follow-up in one live thread.

Voice and text Codex or Claude host Live run stream
View on GitHub Install guide Launch kit Support Trust model
Why it feels different

A phone interface for work that still runs on your machine.

MOBaiLE keeps the powerful part on the host and makes the phone good at capture, follow-up, and recovery. You get remote control without hiding where the work is happening.

Uses your real workspace

Your repo, shell, auth, files, and network stay where the work already happens.

Keeps the run readable

Prompt, progress, result, and next step stay together instead of collapsing into a final notification.

Fits quick mobile moments

Voice mode, silence-based send, widgets, haptics, and Shortcuts make it usable away from the desk.

Makes access explicit

Safe mode, full-access mode, pairing, and the network path stay visible instead of hidden behind vague claims.

Set it up in a few minutes

The shortest path is to run the installer on the computer you want to control, keep the default answers, then pair the iPhone with the QR it shows. 

curl -fsSL https://raw.githubusercontent.com/Vemundss/mobaile/main/scripts/install.sh | bash -s -- --yes
  1. Run the installer on your Mac or Linux machine.
  2. Keep the defaults: Full Access, Anywhere with Tailscale, and usually Yes for the background service.
  3. Open MOBaiLE on iPhone and tap Scan Pairing QR.
  4. Send a small prompt and keep going in the same thread.
  5. Run mobaile first-run to prove the thread.
  6. Run mobaile demo to create a sanitized proof artifact.
Full setup guide Launch kit

Know what runs where

The phone starts and follows the run. Your computer does the work. That split is intentional and stays clear in the product and the docs.

  • The iPhone app does not execute code on-device.
  • Prompts, audio, attachments, and session metadata go to the backend you configure.
  • Use safe mode on a cautious host, or full-access on a trusted private machine.
  • Pairing uses a one-time pair code; the long-lived API token stays on the host.
Privacy policy Trust model Security policy
Product tour

Three moments that make the app feel dependable.

The experience needs to feel legible at a glance: getting oriented, following a run, and sending the next voice task without losing context.

Ready chat showing runtime, working directory, and the composer

Start in the right workspace

See the runtime, working directory, and chat switcher before you send the first prompt.

Live run thread showing the result and the next recommended step

Follow the run live

Stay with the result, summary, and next recommended action in the same thread that launched the work.

Voice capture controls that stay attached to the current thread

Keep talking without losing context

Voice mode reopens the mic after each reply while typed follow-up and attachments stay in the same conversation.

For local-agent users

MOBaiLE is built for people who already trust a local Mac or Linux environment and want phone-native control over the agents running there. Your host keeps the repo, shell, credentials, files, and network.

Proof without private logs

Backend activity events can be exported with mobaile demo as a Markdown or JSON replay. The export omits raw logs, stdout, stderr, prompts, file paths, and tokens by default.

Marketing plan Launch kit Demo command
Search guides

Specific answers for the way people look for this.

These pages explain the concrete setups MOBaiLE is built for: Codex, Claude Code, self-hosted phone control, Tailscale reachability, and explicit access modes.

Codex from iPhone Control Codex CLI work from your phone while the host keeps the repo. Claude Code from iPhone Start and follow Claude Code runs without moving work off the host. Self-hosted phone agent Use iPhone as the control surface for a backend you operate. Tailscale setup Reach the paired host from iPhone without opening a public port. Safe vs full access Choose the host policy that matches the machine you trust.

Need help?

Most setup issues come down to backend health, the saved URL, the API token, or a remote path that is not reachable from the phone.

Support page GitHub issues

Open, inspectable, and self-hostable

The backend, setup scripts, public docs, and issue tracker live in the public repository so you can inspect and install the host-side runtime before you trust it.

Backend repository Contributing