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 sessions in the same dashboard.
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 | — | Stays codex resume-able |
| Runs beside Claude Code | Separate tool | One sidebar for both engines |
Termdeck-started Codex sessions stay natively resumable in the terminal — real cwd, native storage, no lock-in.
Codex web UI, answered
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.
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 — that's the point. Choose the engine per chat and manage both from one sidebar, transcript, and fleet board.