0xcaff/codex-web
a browser frontend for codex desktop, running on a machine you control.
What is codex‑web?
codex‑web is a tiny web‑server that lets you run the Codex Desktop AI‑agent application from any browser while the actual work stays on a machine you control (your laptop, a home server, a cloud VM, etc.). In practice it:
- Starts a Node.js server that serves a web UI.
- Connects that UI to the codex CLI (the command‑line client for the Codex Desktop agent platform).
- Keeps the heavy‑lifting – file access, credential use, command execution – on the host machine, not in the browser.
The result is a thin wrapper that makes the desktop‑only experience reachable from phones, tablets, or any remote computer without having to install the full desktop UI there.
Why does it exist?
The original Codex Desktop runs in a terminal window, which is inconvenient for long‑running agents or for using the tool on devices that don’t have the desktop client installed. By exposing the UI over HTTP, you can:
- Leave agents running after you close your laptop.
- Re‑connect from any device with a browser.
- Keep the backend on a trusted machine, preserving access to local files, credentials, and the signed‑in OpenAI account.
How to get it running
- Prerequisite – have the
codexCLI installed and signed in on the host machine (codex login --device-auth). - Start the server – either with
npxor via Nix:npx --yes github:0xcaff/codex-web # one‑liner, no install needed # or nix run github:0xcaff/codex-web - Open
http://127.0.0.1:8214(or the address you configured) in a browser.
Advanced: proxying to an external app‑server
If you want the Codex app server to run independently of the web wrapper (so a crash of codex‑web doesn’t kill the agent process), you can start the app server manually and point codex‑web at its Unix socket using the provided codex_remote_proxy script. The README includes the exact command sequence.
Security considerations
Because the web UI can issue any command the host user can, any network peer that can reach the server gains full control of the host. Recommendations:
- Run the server only on trusted networks.
- Put it behind a VPN, WireGuard, Tailscale, or an SSH tunnel.
- Add an external reverse‑proxy or authentication gateway if you need stricter access control.
Current features
- Works on macOS, Linux, and any platform where the
codexCLI + Node run. - Browser‑based UI (thin wrapper, fast to update).
- Supports Codex Desktop capabilities such as:
- Subagents – agents that can spawn other agents.
- Inline images – visual output directly in the UI.
- Editor side‑panel – a code editor embedded in the web view.
- Transcription – speech‑to‑text integration.
Roadmap (what’s missing)
- Browser panel – likely built with iframes to embed additional web content.
- Linux computer‑use integration – enabling the agent to control a Linux desktop.
- Terminal support – interactive shell access via the browser.
- Git worker integration – tighter Git operations.
- General community‑driven improvements.
Who’s it for?
- Developers who already use Codex Desktop and want a portable, browser‑based UI.
- Teams that need agents to run on a central, always‑on machine while users interact from anywhere.
- Anyone comfortable handling the security implications of exposing a powerful local agent over the network.
Alternatives mentioned
- pocodex – an earlier project lacking subagents and inline image support.
- Codex Remote (built‑in feature flag) – works over SSH but requires the desktop client on the client side, so it isn’t mobile‑friendly.
- OpenAI’s upcoming mobile app – not yet released;
codex‑webfills the gap for now.
How to contribute or get help
- Open an issue on the repository for bugs or feature requests.
- Share interesting use‑cases on X (Twitter) and tag
@0xcaff. - For commercial or heavily‑customized deployments, the author invites direct contact via email.
TL;DR
codex‑web is a minimal Node.js server that turns the Codex Desktop AI‑agent platform into a browser‑accessible UI while keeping all execution on a trusted host. It’s useful for remote, mobile, or multi‑device access, but you must protect the server because it grants full host control to anyone who can reach it.
Related
- Project
- Project
- Project
- Project