Repository navigation
v0.1.0 — first release
Opt-in dual-agent development workflow: Claude Code plans and reviews, Codex implements headlessly, git is automated, and merging stays a human decision.
Nothing runs until you type the command — installing the skills changes nothing about ordinary Claude Code usage.
What is in this release
/pair [fast|strict] <task>— the main workflow. Claude writes a handoff (goal, constraints, acceptance criteria — deliberately not the implementation approach), branches, hands off to Codex via stdin, runs the project's real quality gates, then reviews the diff with a fresh read-only subagent. Fix and review loops are capped at 2 rounds each./pair-review [codex] [base <branch>]— standalone second pair of eyes on current changes, optionally merging Codex's native reviewer.- Deterministic gates — format, lint, typecheck, test. Exit codes decide; an agent claiming "tests pass" is never trusted.
- Sandbox pinned explicitly on every
codex exec, never inherited from~/.codex/config.toml— headless runs disable approvals, so the sandbox is the only remaining boundary. - A commit at every gated checkpoint — one for the implementation, one per review round, so the branch carries a readable trail and can be merged as-is.
- Tiered dependency policy — project-local installs are self-service, package-manager caches are granted explicitly via
--add-dir, and anything system-level (brew, global installs,sudo, runtimes, containers) stops and asks.
Install
git clone https://github.com/hyj28/claude-codex-pair.git
cd claude-codex-pair && ./install.shRequires the Claude Code CLI, the Codex CLI, and git. Verified against Codex CLI 0.145.0 — the -s, --add-dir, and resume --last flags are version-sensitive.
See WORKFLOW.md for the design doc.