termdeck
Does Codex CLI have a web interface?
Not on its own. Termdeck adds one: it scans your Codex session rollouts, decodes the compressed .jsonl.zst files, and renders the transcript and diffs in the browser.
Termdeck for Codex
A web UI for OpenAI Codex CLI.
Codex CLI runs in your terminal and stores each session as a rollout on disk. Termdeck reads those rollouts and streams them to the browser: follow the transcript, read every diff, and pick up a run from your phone. And it sits right next to your Claude Code and Grok sessions in the same dashboard. Design the UI with Codex while Claude writes the backend, VSCode-style chats with three engines in one window. Every session on every machine, one console.
Compare
Codex CLI alone vs. Codex + Termdeck
| Codex CLI (terminal) | Codex + Termdeck | |
|---|---|---|
| Where it runs | Your machine | Your machine, unchanged |
| Read a session | Terminal scrollback | Streamed to any browser / phone |
| Compressed rollouts | Raw .jsonl.zst on disk | Decoded & rendered for you |
| Diff review | Plain text | Every edit as a readable diff |
| CLI round-trip | n/a | Stays codex resume-able |
| Route work by cost | One subscription takes every task | Easy tasks → Codex, hard ones → Claude (or the other way round) |
| Multiple accounts | One login at a time | One-click switch, live limits per account |
| Runs beside Claude & Grok | Separate tool | One sidebar with Claude Code and Grok |
Termdeck-started Codex sessions stay natively resumable in the terminal: real cwd, native storage, no lock-in.
FAQ
Codex web UI, answered
Will using Termdeck break terminal resume?
No. Sessions Termdeck starts keep their real working directory and native storage, so codex resume <id> still works from the terminal. It re-syncs terminal appends before every web turn.
Can I run Codex and Claude Code together?
Yes, and that is the point. Choose the engine per chat and manage Claude Code, Codex, and Grok from one sidebar, transcript, and fleet board.
Can I route easy tasks to Codex and hard ones to Claude?
Yes. Pick the engine per chat in the same window: routine work on the cheaper plan, hard problems on the premium one. Routing by task instead of upgrading a plan to absorb overflow is how the right split saves up to $500 a year.
100+ engineers at five companies that asked not to be named. Their managers watch the spend.