Codex Remote Control LabControl your desktop Codex session from your phone

Keep Codex bound to localhost, expose only a token-protected LAN bridge, and continue the same thread across PC and mobile.

Start the Bridge

Security Model

Localhost-first

The Codex app-server examples bind to 127.0.0.1. The LAN-facing surface is the Node bridge.

Phone remote

Your phone browser can operate the desktop Codex app-server through the token-protected bridge.

Session sync

Share one bridge-managed thread between desktop and phone, so the same Codex work continues on either device.

Public-safe

Token files, uploads, local Codex homes, logs, and session databases are ignored and documented as local-only.

Codex Remote Control Lab

Quick Start

bash

npm ci
npm run phone

Open the printed URL from a phone or another browser on the same Wi-Fi/LAN. The phone can drive the desktop Codex session, and another browser can resume the same bridge-managed thread.

For protocol-only testing, run the app-server and probe from separate terminals:

bash

npm run server:ws
npm run probe:ws

Layout

text

phone browser -> http://Mac-LAN-IP:45214 -> Node bridge -> ws://127.0.0.1:45213 -> Codex app-server

The app-server remains local. The bridge requires a token on page, API, and WebSocket requests.