How do I start a coding agent task on my laptop and continue it on my phone?
To continue a coding-agent task on your phone, connect to the same running session through a supported remote interface, rather than start a new conversation. Keep the execution host online and secure the connection. The phone can display results and send instructions; remote access does not move execution off your laptop.
Last checked against Omnigent v0.19.0 · 2026-10-23
What must stay online to use a coding agent from my phone?
To continue a laptop coding-agent session on a phone, you need a reachable interface, access to the right account or terminal, and an execution machine that stays online. These are separate requirements. A remotely hosted chat page can remain readable after a laptop disconnects, even though the coding process on that laptop cannot do more work.
Keep a known session link or terminal identifier. Starting a fresh chat with the same model does not restore the previous conversation. Before leaving, check the actual connection from your phone, confirm that you see the intended session, and decide whether new instructions may change files or need approval.
For example, start investigating a failing parser test at your desk. From your phone, read the reported failure and ask whether the empty-input case also fails on the base revision, without changing files. That follow-up needs the original task state. It does not require running a coding CLI on the phone itself.
How can I access a coding-agent session from my phone?
SSH with a persistent terminal such as tmux is sufficient when you want the original CLI and can manage remote access. tmux lets you detach and reattach the terminal session; SSH supplies the connection. You still need to secure the host, keep it awake, and tolerate a terminal-sized interface on a small screen.
Claude Code Remote Control is a native option for continuing a local Claude Code session through its supported web or mobile interface. Its documentation distinguishes remote access from cloud execution: the local environment still does the work. Check current account and version requirements rather than assuming every local CLI has an equivalent feature.
Codex Cloud is another option when you want work in a configured cloud workspace, with web, mobile, or desktop continuation. That can run without the laptop, but it is a different execution environment, not remote access to an arbitrary existing local CLI process.
Omnigent’s shared browser interface is an option when you work with multiple supported harnesses or want conversation-level navigation instead of SSH terminal access. Unlike a cloud task, opening a session on your phone does not move its execution environment. Compare what the interface exposes, how it authenticates, and which machine actually runs tools. For work that must survive a closed laptop, start on an appropriate always-on host or configured cloud environment; changing the viewing device is not migration.
How do I continue an Omnigent session on my phone?
To continue a laptop coding-agent session on your phone through Omnigent, open the same reachable server in your phone browser and return to the existing session. Sign in to the same account when authentication is enabled. You can read the conversation and send follow-ups while the execution host remains available; the web interface also provides supported views of subagents, terminals, and files.
On a trusted local network, configure the server’s LAN interface before starting the session, for example with omnigent server --host <LAN-IP>. The default bind is 127.0.0.1, which another device cannot reach. Non-loopback binds enable sign-in by default unless explicit authentication settings override it. Open the laptop’s LAN address, not localhost on the phone. Test access from your phone with the same account before starting work.
Away from that network, use a securely configured reachable deployment or private network connection. Do not expose an unauthenticated development server just to reach it remotely. A page that will not load suggests a connection problem; a loaded server missing your session may be the wrong server or account.
If a laptop-hosted session stops because the machine sleeps, opening it on your phone does not wake it or move the process elsewhere. A cloud-hosted server still depends on the laptop when that laptop is the execution host. Restore that connection or plan a new session on an always-on host with the repository and required inputs configured there.