How do I start a coding agent task on my laptop and continue it on my phone?

Summary

• Start the task with Omnigent, an open-source meta-harness ("Status: alpha"), for example omnigent claude. Terminal, browser and phone are views of the same session, so messages, sub-agents, terminals and files stay in sync.
• 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. From anywhere, deploy an Omnigent server and register your laptop as a host with omnigent login and omnigent host.
• The agent keeps running on its host. A laptop host is only available while the machine is on, and a cloud sandbox host keeps running when it is off.
• From the phone you can chat, monitor sub-agents, browse files, view code changes, leave inline comments and answer pending approvals.
• On Databricks ("Omnigent is in Beta"), you sign in with your workspace identity and open <workspace-url>/omnigent.

How do I start a coding agent task on my laptop and continue it on my phone?

Run the agent through an Omnigent server that your phone can reach, then open that server on the phone. Omnigent is an open-source meta-harness for Claude Code, Codex, Cursor, OpenCode, Hermes, Pi and custom agents (Apache 2.0, README badge "Status: alpha"). Its sessions follow you: "start in your terminal, continue in the browser, pick it up on your phone." The phone is a client of the server, and the agent keeps executing on its host, which is your laptop unless you move it to a cloud sandbox host.

What are the steps?

1. Install Omnigent. It needs Python 3.12 or newer:

curl -fsSL https://raw.githubusercontent.com/omnigent-ai/omnigent/main/scripts/install_oss.sh | sh

2. Start the task in your terminal, for example omnigent claude or omnigent codex. Either command also opens a web UI at http://localhost:6767 that shows the same session.
3. Open the session on the phone with one of the routes in the table below.
4. To reach the server from anywhere, deploy it and register your laptop as a host. login authenticates you, and host registers your machine so the server can dispatch agent work to it:

omnigent login https://your-host
omnigent host https://your-host

Which route should you use from the phone?

Route	When to use it	What you need
Mobile web UI on the same Wi-Fi	A quick check at home or in the office	Your machine's LAN address, such as http://192.168.x.x:6767. localhost:6767 is reachable only from the machine running the server
Mobile web UI on a deployed server	Away from your desk	A server with a stable URL. The web UI is an installable web app, so you can add it to the home screen
iOS or Android app	An installed app instead of a browser tab	A reachable server. The iOS app requires an https:// URL and rejects plain http://

The iOS app is a thin native shell around the server-served web UI. It shows notifications and a badge only while the app is open, because it does not poll in the background. A server that is reachable beyond your own network should require sign-in. Omnigent supports multi-user accounts, turned on with OMNIGENT_AUTH_ENABLED=1, and the Docker deploy enables it by default.

What can you do from the phone?

The mobile experience is the full web UI, touch-optimized: chat, monitor sub-agents, browse files, view code changes and leave inline comments. You can also answer the prompts that pause the agent, which cover policy approval gates, harness permission prompts, questions the agent asks you and plan review. The tutorial's own example is to "answer an approval prompt from the coffee line." The session owner and Edit collaborators can answer prompts, and Read viewers cannot see or answer them.

What are the limits?

• Host availability. The web, terminal and mobile interfaces all talk to the server, never to the runner directly, and the runner executes the agent on the host. If the host is your laptop, it must stay on. A cloud sandbox host removes that dependency.
• No offline mode. The web UI needs a connection to your server and does not cache pages for offline use.
• Sharing is code execution. Only share Edit with people you trust to run arbitrary code on your machine.

How Databricks approaches this

Omnigent on Databricks (Beta) is a managed deployment. Databricks operates the server and integrates it with your workspace identity provider, so you sign in with your Databricks identity and have no separate Omnigent account. Open <workspace-url>/omnigent, select New session, and pick a host. A Databricks Sandbox host runs in the cloud, keeps running when your laptop is off, and keeps your credentials inside Databricks. A host on your own machine is available only while the machine is on and the omni host process is running:

omni login <workspace-url>
omni host --server <workspace-url>

For the phone, install the Omnigent mobile app or use the mobile web UI in a phone browser, then enter your workspace URL. If your workspace uses an IP access list, phones must connect from an allowed IP address, which admins typically arrange through a corporate VPN. Each session is private to its owner until shared.

FAQs

Can I get back to the same session on my laptop?

Yes. Every interface connects to the same persistent, shareable session, so you can keep going anywhere. In the terminal, resume it with omni resume <conversation_id>.

What happens if my phone loses its connection?

The phone is only a client. The runner on the host keeps executing the agent, and sessions persist across browser refreshes.