openai/codex

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.