For developers
Codex
Run OpenAI Codex sessions under the Viewport daemon. Session detection, plan adapter, hook bridge.
BetaWired and usable, but the surface may shift before 1.0.
The Codex adapter is wired but has fewer polish steps than Claude Code. Sessions stream correctly; plan templates work; permission gates are CLI-level rather than fine-grained.
How it's wired
- The Codex CLI exposes session lifecycle hooks via its config file (
~/.codex/config.toml). - Viewport's
vpd installwrites a hook entry that posts session events to the local daemon. - Frames flow through the same path as Claude Code (local socket → daemon → relay → platform).
Install
vpd installYou'll see:
[+] codex found at /usr/local/bin/codex
[+] Installing Codex hook... appended to ~/.codex/config.tomlVerify:
cd ~/code/api
codex "fix the failing auth tests"In a separate terminal:
vpd logs --followYou should see session frames.
Plan template
Codex's plan-then-execute mode is similar in shape to Claude Code's. Override the template per-workflow:
plan_template: ./prompts/codex-plan.mdIf no template is supplied, Viewport uses a generic plan structure (goal / steps / files / risks).
Differences from Claude Code
| Capability | Claude Code | Codex |
|---|---|---|
| Per-tool permission prompts | Fine-grained | CLI-level (whole session) |
| Sub-agent nesting | Partial (flattened) | N/A |
| Streaming transcript | Yes | Yes |
| Cost tracking | Per-session | Per-session |
| Hook installer | First-class | First-class |
For most flows the experience is interchangeable. If you need fine-grained permission gating, Claude Code is the better target today.