Codex doesn't stop.Neither should you.
NemoDock is the mobile command center for your Codex sessions — projects, approvals, replies, and spawned agents, always within reach.
NemoDock
Projects
codex_sessions_app
2 min ago · session #48
Runtime pairing complete. Continue with next sync step?
nemodock_middleware
8 min ago · session #21
Allow runtime to proceed with database migration?
runtime_companion
running · session #33
Sri MacBook Pro · paired & ready
Two pieces. One system.
NemoDock is a phone app and a desktop companion working together. The companion runs on your machine and bridges your Codex sessions to your phone — no ports open, no credentials shared.
NemoDock
iPhone / Android
Desktop Companion
macOS · Windows · Linux
Codex app-server
Local · your machine
Built around the real shape of Codex work.
Not a chat screen. Not a notification drawer. NemoDock is structured around projects, sessions, agents, blocked steps, and runtime ownership.
One dock for every Codex workspace
Projects, sessions, approvals, replies, and spawned agents — everything that matters, in one place, on your phone.
Your runtime stays exactly where it belongs
Your laptop, desktop, or server remains the execution host. NemoDock routes actions back to the paired machine that owns the session.
Control surface. Not execution surface.
The phone directs. The paired runtime executes. Codex credentials and turn execution never leave the machine that should own them.
Reduce interruption cost without losing the trust boundary.
Stay in control of active Codex work from anywhere. Execution and credentials stay with the paired runtime that should own them.
See what needs you — instantly.
Reply-required and approval-required sessions stay visually distinct. Triage in seconds, not minutes. No scanning. No guessing.
Projects, sessions, agents — all connected.
Organized around how Codex actually works: projects first, sessions inside them, spawned agents visible beneath. Not a flattened chat surface.
Keep work moving away from the desk.
When a session pauses for a reply or approval, act from your phone instead of waiting to get back to the laptop.
Credentials stay where they belong.
NemoDock app auth identifies the user. The paired runtime keeps its own Codex login. Middleware checks ownership before forwarding any action.
Three steps. Work keeps moving.
Designed for fast understanding, fast decisions, and clean continuation — exactly when a session would otherwise stall.
Install the Desktop Companion on your machine
Download for macOS, Windows, or Linux. It runs quietly in the background, connects outbound to NemoDock, and never opens a port on your machine.
Pair your phone in seconds
Open NemoDock on your phone, tap Pair Runtime, scan the QR code shown in the companion. Your projects and sessions appear immediately.
Reply, approve, and keep work moving
When a session needs you, act from your phone. The companion forwards the action to your local Codex app-server and the turn continues — exactly where it should.
The questions that matter.
Direct answers to what builders actually want to know about how NemoDock works, what it touches, and what it never does.
What is NemoDock?
NemoDock is a mobile command center for Codex work. It lets you monitor projects, inspect sessions, review spawned agents, and respond to blocked work from your phone — without needing to be at your laptop.
Does NemoDock run Codex on the phone?
No. The phone is the control surface. The paired runtime host still owns execution and communicates with the local Codex app-server. Nothing heavy runs on mobile.
Why is runtime pairing part of the product?
Because the phone should not need direct access to a laptop port or long-lived Codex credentials. Pairing binds an authenticated user to a specific runtime in a safer, explicit way — so you control what executes, not just what you see.
How does NemoDock help in practice?
It reduces interruption cost. Instead of discovering later that a session was waiting on a reply or approval, you can act on it immediately from anywhere and keep the work moving.
What happens if the runtime is offline?
You can still inspect the last synced session state. New replies or approvals queue but cannot execute until the owning runtime reconnects and confirms availability.
Do I need to log into Codex on the phone?
No. NemoDock app auth and Codex auth are intentionally separate. The runtime retains its own Codex login. The phone never touches those credentials.