wip-codex-remote-control

WIP Computer

Codex Remote Control

Drive your local Codex session from your phone.

Your Codex session is running on your laptop. You step away. You want to keep going from your phone.

Codex Remote Control bridges the two: streamed events, prompt input, and a stop button, on the phone.

Alpha status

This is a transport prototype, not a launch-ready feature. The wire shape, pairing, and Kaleidoscope phone surface are deployed and working, but two product blockers must close before this is safe for real work:

• Not end-to-end encrypted yet. Traffic is TLS to wip.computer, but the relay sees plaintext WebSocket frames. WIP can currently inspect prompts, Codex events, command output, and errors. End-to-end encryption between the phone and the local daemon is planned (Phase 2.5). Until then, treat this alpha as a wire-test, not a private channel.
• No real session attach yet. When the phone opens a URL for an existing Codex thread, the daemon currently starts a new daemon-owned thread instead of attaching to the listed one. The "same session, same context, same files" promise is the target, not the current behavior. Real attach/resume is planned (Phase 3).

While those land, the alpha is useful for: validating the local daemon shape, the relay endpoints, and the phone UI; iterating on pairing UX; smoke-testing protocol changes. It is not useful for: dogfooding real coding work, or any scenario where the relay reading payload content would be a problem.

Tracking: wip-ldm-os-private/ai/product/plans-prds/codex-remote-control/2026-04-28--cc-mini--codex-remote-control-master-plan.md.

Teach Your AI to Install Codex Remote Control

Open Codex (or any AI) and paste this:

Read https://wip.computer/install/wip-codex-remote-control.txt

Check if it's installed. If yes, show me what version I have.

If not, walk me through setup and explain:

1. What is Codex Remote Control?
2. What does it install on my system?
3. How does my phone drive my Codex session?

Then ask:
- Do you have questions?
- Want to see a dry run?

If I say yes, install via `ldm install --alpha wip-codex-remote-control` and walk me through pairing my phone.

Don't install anything until I say "install".

That's it. Your AI reads the spec, checks what you have, and walks you through a dry run before touching anything.

Features

• Drive Codex from your phone. A new daemon-owned thread, on your phone, in real time. (Attaching to existing local Codex threads is planned, not yet implemented.)
• Streamed events. Agent messages, command runs, reasoning, every event from runStreamed arrives on the phone as it happens.
• Stop button. Interrupt the current turn from the phone. The daemon aborts the underlying Codex turn cleanly.
• No port forwarding. The daemon dials out to wip.computer; the phone connects in. Works on any network. No NAT punching, no firewall holes, no LAN.
• Passkey auth. Sapien ID. Sign in once on your phone with Face ID. Drive any session from any device you're signed in on.

Planned (not yet shipping):

• End-to-end encryption between the phone and the local daemon. The wip.computer relay routes ciphertext only.
• Same-session attach. Open a URL for an existing local Codex thread and drive that thread, not a new one.
• Single-use relay tickets for the browser WebSocket, replacing the current ?token= URL parameter.

More Info

• Architecture, protocol surface, and technical details
• Universal Interface Spec ... The six interfaces every agent-native tool can ship

License

Dual-license model designed to keep tools free while preventing commercial resellers.

MIT      All CLI tools, MCP servers, skills, and hooks (use anywhere, no restrictions).
AGPLv3   Commercial redistribution, marketplace listings, or bundling into paid services.

AGPLv3 for personal use is free. Commercial licenses available.

Can I use this?

Yes, freely:

• Use any tool locally or on your own servers
• Modify the code for your own projects
• Include in your internal CI/CD pipelines
• Fork it and send us feedback via PRs (we'd love that)

Need a commercial license:

• Bundle into a product you sell
• List on a marketplace (Claude Marketplace, OAI GPT/Apps, Clawhub.ai, VS Code, etc.)
• Offer as part of a hosted/SaaS platform
• Redistribute commercially

Using these tools to build your own software is fine. Reselling the tools themselves is what requires a commercial license.

By submitting a PR, you agree to the Contributor License Agreement.

Built by Parker Todd Brooks, Lēsa (OpenClaw, Claude Opus 4.7), Claude Code (Claude Opus 4.7).

WIP.computer. Learning Dreaming Machines.