An opinionated Codex CLI. This is strictly a personal hobby project, forked from openai/codex.
Choose one of these two ways:
- Install from npm:
npm i -g @loongphy/codext- Build from source:
cd codex-rs
cargo run --bin codexFull change log: see CHANGED.md.
-
Ctrl+Shift+Cin the TUI composer copies the current draft to the system clipboard;Ctrl+Ckeeps its existing behavior, and empty drafts still fall back to the oldCtrl+Cpath. -
TUI status header with model/effort, cwd, git summary, and rate-limit status.
-
Collaboration mode presets accept per-mode overrides and default to the active
/modelsettings. Example:# config.toml [collaboration_modes.plan] model = "gpt-5.4" reasoning_effort = "xhigh" [collaboration_modes.code] model = "gpt-5.4"
-
TUI watches
auth.jsonfor external login changes and reloads auth automatically, with a warning on account switch. This works well with codex-auth when you refresh or switch login state outside the TUI. -
AGENTS.md and project-doc instructions are refreshed on each new user turn, and Codex shows an explicit warning when a refresh is applied.
We will never merge code from the upstream repo; instead, we re-implement our changes on top of the latest upstream code.
Iteration flow (aligned with .agents/skills/codex-upstream-reapply):
flowchart TD
A[Freeze old branch: commit changes + intent docs] --> B[Fetch upstream tags]
B --> C[Pick tag + create new branch from tag]
C --> D[Generate reimplementation bundle]
D --> E[Read old branch + bundle for intent]
E --> F[Re-implement changes on new branch]
F --> G[Sanity check diffs vs tag]
G --> H[Force-push to fork main]
When syncing to the latest upstream codex version, use .agents/skills/codex-upstream-reapply to re-implement our custom requirements on top of the newest code, avoiding merge conflicts from the old branch history.
Example:
$codex-upstream-reapply old_branch feat/rust-v0.94.0, new origin tag: rust-v0.98.0
Status bar design reference: https://linux.do/t/topic/1481797
