How to control my coding agents from my phone?

Summary

• Run your agents under a server your phone can reach, then connect from a mobile client; the agent keeps executing on its host.
• Omnigent, an open-source meta-harness, makes the same session accessible on terminal, browser and phone at once, through an iOS app, an Android app or the touch-optimized mobile web UI.
• From the phone you can chat with the agent, monitor sub-agents, browse files, view code changes, leave inline comments and answer pending prompts such as policy approvals.
• On Databricks, the Omnigent mobile app or a phone browser connects to your workspace URL with your Databricks identity. The open-source project lists "Status: alpha"; on Databricks, "Omnigent is in Beta".

How to control my coding agents from my phone?

Put the agents behind a server your phone can reach and connect to it from a mobile client. With Omnigent, an open-source meta-harness for Claude Code, Codex, Cursor, OpenCode, Hermes, Pi and custom agents, the same session is open on your terminal, browser and phone at the same time. The agent keeps running on its host; the phone shows and steers the session. Some agents ship their own remote option too: Claude Code's Remote Control connects claude.ai/code or the Claude app for iOS and Android to a Claude Code session on your machine.

What does controlling a coding agent from a phone involve?

A host (your laptop, a VM or a cloud sandbox) runs the agent loop and its tools. A server coordinates sessions. The phone is a client: Omnigent's iOS app is a thin native shell around the server-served web UI and doesn't host sessions itself. So the host must be running and the server must be reachable from your phone's network.
What you can do from the phone:

• Follow the work: messages, tool calls and file changes stream to every connected viewer.
• Answer pending prompts: policy approvals, harness permission prompts, questions from the agent, plan review and MCP forms.
• Review output: browse files, view code changes and leave inline comments.
• Hand off: share the session with a teammate at Read or Edit permission.

Key capabilities to evaluate

Capability	Why it matters	What Omnigent documents
One session across devices	No restart when you switch screens	Terminal, browser and phone show the same session, synced in real time
Mobile clients	Not everyone wants another app	iOS app, Android app, mobile web UI, and an installable web app (PWA)
Approvals on the phone	Risky actions can't wait for a desk	A policy can return ASK, which pauses the action until the owner or an Edit collaborator approves or rejects it
Host independence	Closing the phone app shouldn't stop the agent	Sessions run on a host; a server-provisioned cloud sandbox means no laptop has to stay online
Notifications	You need to know the agent is waiting	The iOS app shows foreground notifications and a badge while open; it doesn't poll in the background
Connectivity	Mobile networks drop	The web UI has no offline mode and needs a connection to your server

How do you reach Omnigent from your phone?

1. Install Omnigent with curl -fsSL https://raw.githubusercontent.com/omnigent-ai/omnigent/main/scripts/install_oss.sh | sh (it needs Python 3.12 or newer).
2. Start an agent, for example omnigent claude or omnigent codex. The web UI starts with every session, locally at http://localhost:6767.
3. On the same Wi-Fi network, open your machine's LAN address in the phone's browser, such as http://192.168.x.x:6767.
4. From anywhere, deploy the Omnigent server with a stable URL (see the repository's deploy guide), then sign in and register your laptop as a host:

omnigent login https://your-host   # sign in once
omnigent host  https://your-host   # new sessions can now run on this machine

5. Install the iOS or Android app and enter the server URL. The iOS app accepts only https:// server URLs.

A network-exposed server should require sign-in: set OMNIGENT_AUTH_ENABLED=1 for built-in accounts, or configure your identity provider through OIDC.

How Databricks approaches mobile agent control

On Databricks, Databricks operates the Omnigent server and you sign in with your workspace identity. Install the Omnigent mobile app from the App Store or use the mobile web UI in any phone browser, then enter your workspace URL. Your workspace's front-end network controls still apply: with an IP access list, phones must connect from an allowed address, which admins typically handle by routing mobile traffic through a corporate VPN. A Databricks Sandbox host (Beta) keeps running when your laptop is off. Each session stays private to its owner until shared, and Edit access lets a collaborator run shell commands and modify files on the host through the agent, so grant it carefully.

FAQs

Do I need a native mobile app?

No. The mobile web UI works in any phone browser and can be added to your home screen as a web app. Native iOS and Android apps are also available.

Can I approve risky operations from my phone?

Yes. When a policy returns ASK, the action pauses until someone who can drive the session approves or rejects it. Read-only viewers can't see or answer these prompts.

What happens if my phone loses its connection?

The agent keeps working on its host, because the phone only displays the session. The web UI has no offline mode, and sessions persist across browser refreshes, so you can pick the session up again once you reconnect.

Can I redirect an agent from my phone?

Yes. Send a follow-up and it waits in the queue, or tap Steer to deliver it mid-turn. To move a conversation to a different agent, clone the session and pick the new agent for the fork.