Remote control for Claude Code, from anywhere

Pair your phone with the daemon on your machine. Watch live sessions, approve tool calls, and review diffs while Claude Code and Codex keep running locally — not in our cloud.

Your agent is on the laptop you left behind

Claude Code and Codex do their best work on your development machine — full repo access, local tools, your env. The friction starts when you are not at the keyboard: a meeting, a commute, dinner, sleep. You still want progress, permission prompts answered, and diffs reviewed without SSHing from a phone browser.

Search for Claude Code remote control or Claude Code mobile and you will find product pages, forum threads, and first-party experiments. The underlying need is the same: keep the agent on your hardware, put the control surface in your pocket.

How SeaWork remote control works

SeaWork is a local-first control plane. A daemon on your machine owns the agent process; the mobile and desktop apps are the remote UI. We do not host your repo or run Claude Code for you.

Pair your own machine: install the daemon, link the app, stay on your hardware
Live session view: stream status, tools, and progress while agents run
Approve tools from your phone: permission prompts without racing back to the laptop
Review diffs on the go: steer long runs and check changes before you merge
E2E encrypted remote path: optional relay for access away from LAN; code stays on your machine

How it works in three steps

Honest setup: the daemon and agent runtime run on your own machine; remote access uses the E2E-encrypted SeaWork relay by default, or a direct/custom connection. You connect to your machine, not a hosted agent farm. Your computer must be on and the daemon running for remote sessions to work.

1. Install the daemon on your machine

Download SeaWork for your OS, install the desktop app or CLI, and start the local daemon. It manages Claude Code and Codex processes on the same machine that holds your repos.

2. Pair your phone

Open the SeaWork mobile app and pair it with the daemon. Once linked, the phone becomes a remote control for agents that still execute on your laptop or workstation.

3. Remote control the session

Start or resume agents, watch live progress, answer tool approvals, and review diffs from anywhere you have connectivity. Remote control needs your machine awake and the daemon running; a dropped phone connection does not necessarily stop an agent that is already running.

Claude Code and Codex on one control plane

SeaWork supports Claude Code, OpenAI Codex, and Grok Build as first-class local agents. Use the same remote-control flow for all: one daemon, one phone app, multi-provider sessions without uploading your monorepo to a third-party agent host.

FAQ

Is Claude Code remote control with SeaWork secure?

SeaWork is designed local-first: agents run on your machine. Remote access can use an optional end-to-end encrypted relay so the control channel is not plain open traffic. We do not claim zero-config cloud security — you still own the host, auth, and network surface of your workstation.

Does my code leave my machine?

No for the agent workspace: Claude Code and Codex execute against files on your computer. SeaWork monitors and controls those local processes. Your source does not become a copy on SeaWork servers. Model providers still receive prompts/context per their own APIs when the agent calls them — same as running the CLI at your desk.

Do I need to keep my computer on?

Yes. Remote control requires your machine awake and the daemon running; a dropped phone connection does not necessarily stop an agent that is already running. If the laptop sleeps, shuts down, or the daemon stops, agents stop. SeaWork is not a cloud runner that keeps coding after your machine is off.

Put remote control in your pocket

Download SeaWork, install the daemon, pair your phone, and remote-control Claude Code and Codex without leaving your code on someone else's servers.

Download SeaWork