Discofork
Repository brief

openai/codex

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-29T21:29:00.865Z
1mo ago

openai/codex

openai/codex is a large, actively maintained open source coding agent for terminal use. It has strong traction (68,265 stars, 9,141 forks), a very recent push history, and supports installs via npm, Homebrew, release binaries, IDE integration, and a desktop app path. The repo appears to be a monorepo with Node.js/JavaScript tooling plus Rust components, and it includes docs, CLI, SDK, and build/config infrastructure.

GitHub
Loading tags...
Stars68,265
Forks9,141
Default branchmain
Last pushed2026-03-29T21:24:01Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

6 of 6 fork briefs
Selected

Choose this fork if you want a more ambitious agent platform than upstream Codex CLI, especially for multi-agent, browser, and automation workflows. Stick with upstream if you want the smallest maintenance burden, fastest access to Codex fixes, or the simplest terminal-first experience.

Choose this fork if you want a customized, more opinionated Codex CLI and accept substantial upstream lag. Choose upstream if you want the full, actively maintained feature set and lower maintenance risk.

Prefer this fork if you want the added TUI and workflow customization and are willing to accept meaningful divergence. Stick with upstream if you want maximum compatibility, the broadest feature set, and the lowest maintenance burden.

Choose this fork if your priority is getting Codex working well in Termux/Android and you want the extra platform-specific release and test work. Choose upstream instead if you need the newest Codex features, the broadest platform support, or the least divergence from the main project.

Choose this fork if you value provider flexibility, safety hardening, and custom operational workflows more than staying current with upstream Codex. Avoid it if you want the latest upstream feature set, broad compatibility, and low-maintenance upgrades.

Choose this fork if your priority is multi-agent coordination and you are willing to trade upstream freshness and compatibility for that workflow. Stick with upstream if you want the latest supported Codex CLI behavior, lower maintenance risk, and better alignment with official releases.