MOBaiLE Trust

Your phone controls the run. Your machine does the work.

MOBaiLE is designed around an explicit split: the iPhone captures prompts and follows progress, while the paired Mac or Linux backend owns execution, files, credentials, policy, and network access.

Inspect the backend Product overview Privacy policy

Data flow

What runs where

MOBaiLE should not be described as "no data leaves your devices." Prompts, voice-derived text, attachments, and session metadata go to the backend you pair. Agent providers can still receive prompts through the local Codex or Claude CLI you configure on that host.

On the iPhone

Text prompts, voice capture, attachments, and thread UI.
Saved backend profile and API token in iOS storage.
Live progress, summaries, artifacts, and follow-up controls.

On the host

Backend API, pairing, auth, policy, and run history.
Repo, shell, files, credentials, network, and agent CLIs.
Safe or full-access execution mode chosen during setup.

Pairing is deliberate

The setup flow uses a QR and one-time pair code. The long-lived API token stays host-side and is exchanged only after the app proves it has the fresh pair code.

Access mode is visible

Safe mode restricts workdir and file access. Full-access mode is for trusted private hosts where you intentionally want deeper automation.

The network path is inspectable

MOBaiLE supports same-Wi-Fi, Tailscale, local simulator, and configured public HTTPS paths. Tailscale is the recommended private path for off-Wi-Fi use.

Demo exports are sanitized

mobaile demo uses backend activity events to create a proof artifact while omitting raw logs, stdout, stderr, prompts, file paths, and tokens by default.

Useful commands

mobaile status shows service, access mode, phone path, and pairing state.
mobaile check runs a concise readiness preflight.
mobaile doctor checks pairing URLs, QR state, health, and executor readiness.
mobaile demo --out mobaile-demo.md creates a public-safe proof artifact.