codex-pair skill
A skill that links two to four open Codex CLI windows: one splits the work while the others execute, cross-check and deliver.
- 105 ★ on the repository
- Last commit
Extended access
Why this level
- Several Codex windows change the project in parallel, and the skill can publish changes to a remote repository with the user's explicit permission.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/codex-pairDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Several Codex windows change the project in parallel, and the skill can publish changes to a remote repository with the user's explicit permission.
This is third-party code. Review the repository files before installing.
What it does
codex-pair is a skill for Codex CLI that makes already open windows work on one project. Window A hands out tasks and coordinates, window B accepts an invitation and executes, and if needed A also invites windows C and D, up to four in total. Each window keeps its own session, account settings, model and permissions. Windows exchange tasks, questions and results through a local message bridge. The skill drives the full cycle: A registers small tasks with allowed paths and checks, an executor claims the message, changes only what is permitted and delivers the result. Versions go to independent review and decisions are bound to the exact version, so an old approval does not pass new code. By default executors get separate Git worktrees. Publishing happens only with the user's explicit permission.
Who it is for. Developers who run one project in several Codex CLI windows and want to split work and cross-check results from records.
Good fit when
- A large task is split into independent stages between windows A and B.
- Another window's stage is reviewed by an independent window and the decision is bound to a specific version.
- An executor asks the coordinator a question and keeps the task without losing progress.
- When the limit runs low work is saved in a checkpoint and continues from it later.
Not a fit when
- You need ordinary Git work in one window: starting coordination is pointless.
- You need a stable release: the release is marked preliminary and partly validated.
- You do not work on Windows: Windows is named as the main validated environment.
Example request
$codex-pair — organize windows A and B on the project, split the task into stages and show the invitation for B.Limitations
The current v1.4.0-preview.1 is called preliminary: eight acceptance areas remain open and the overall status is `formal=false`. The main validated environment is Windows, with Python 3.10 or newer, Git and the official Codex CLI supporting `queue` and `app-server` required. Compatibility is confirmed for the listed CLI build, not for any version. The project is personal and not affiliated with OpenAI. Documentation is in Chinese and some decisions are described as not fully closed.
How to disable. Delete the `codex-pair` folder from your Codex `skills` directory. Old version copies sit in `codex-pair-skill-backups`, and the bridge stops with `bridge --action stop`.
FAQ
How do I install the skill?
Run `python scripts/install_skill.py --source . --home <Codex config directory>` from a clone of the repository. The installer copies the skill into `skills/codex-pair`, backs up the old version and leaves login and model untouched.
How do I start working?
In window A call `$codex-pair` and describe the project, goal and permitted changes. The skill returns an invitation that goes to window B.
How many windows can join?
Up to four visible ones. A invites the third and fourth with `invite-member`.
Who reviews the result?
Independent review is bound to the exact version. Work by DeepSeek needs a GPT review from OpenAI or from the apinebula provider, recorded as third party.
Does the skill publish to a remote repository on its own?
No. Publishing needs the user's explicit permission, a confirmed repository, remote branch and a clean working tree.
Discussion
No questions or reviews yet.
Related
SkillsA Claude Code skill that hands implementation-heavy work to Codex CLI while Claude keeps planning, review and acceptance.
A skill that hands work to a team of a CTO, five PMs and fifty engineers: roles, permissions, a task log and resource leases.
A skill that turns several Claude Code, Codex and Cursor windows into a team with a coordinator, shared registry and cross-review
A Codex skill collection: phased planning, parallel subagents, documentation access, a browser, 51 hooks and ready agent roles.
CodexPotter loops Codex with a clean context each round until the code matches the goal, as a replacement for the built-in /goal.
A desktop app where Claude Code, Codex, Gemini and other agents work as a team of specialists in a shared project
README in short
The repository holds the `SKILL.md` skill, the `scripts/pair.py` script and installer, audit schemas, references for the protocol, commands, recovery and auxiliary review, plus validation records and a post-release test list.
README badge
Original SKILL.md
--- name: codex-pair description: 让用户已打开的两个到四个Codex CLI分工、交接和独立审核；下一版候选增加受控恢复、只读诊断及官方GPT辅助池。仅在准确版本能力已验证时启用，不替用户新开可见窗口，不用于普通单窗口Git操作。 --- # Codex Pair 当前安装包版本为 `v1.4.0-preview.1`，属于部分验证的预发行版。整体为 `formal=false / needs_validation`，真实 daemon、双 CLI、transport、可信原生启动、完整系统映像、动态/JIT、正式 Host→Store 和正式调度发行安装共 8 个范围尚未关闭。先读[本版安装与验证说明](references/pre-release-20261110.md)；安装成功不能作为这些范围的放行证据。 本项目只对接官方发布的Codex CLI，保留原账号、模型、权限和用户选定窗口。原生接口未覆盖的控制能力必须明确标注；不以定制CLI、观察事件或提示词代替已验证的执行门禁。官方接口的准确范围见[官方CLI控制](references/official-cli-control.md)。 此目录包含下一版候选。已完成部分断网 Hyper-V 隔离回归，准确范围见 CHANGELOG.md；真实原窗口及完整能力验收仍未完成。先读[本轮状态与缺口](references/next-version-status.md)，以日期较新的实际记录为准；开发或审查这个 skill 不代表启动协作。安装副本一致不代表原窗口或活动桥已加载新版，也不能把接口存在、AST解析或模拟夹具作为真实协作通过的依据。 按用途读参考：阻塞只读查询、暂停、继续及限定恢复用[诊断与控制](references/recovery-v14.md)；辅助审核用[辅助池](references/auxiliary-pool.md)和[审查适配](references/audit-adapter.md)；CLI变化用[兼容性预检](references/cli-compatibility.md)。[182项验收与30项调度规则](references/next-version-matrix.md)逐项保留，全部未判为本轮动态通过。 历史v1.3.0基线支持用户已打开的A/B窗口，可邀请已有C/D及一个受管独立官方GPT审核会话。该基线的正常使用链已有实际验证；当前预发行及历史完整故障矩阵不能沿用这个结论。安装方式见README.md，后续检查见POST_RELEASE_TESTS.md；两份文件已纳入发行清单。安装与实际运行入口分别核对。 先读[命令与输入](references/team-commands.md)，接管测试时读[详细验证交接](references/validation-handoff-four-cli.md)。旧双窗口协议的领取、分页、交付和未知对账仍适用；旧文档“只能两个”“不新建任何模型会话”和9%新轮次默认值仅描述v1.2.1，不能覆盖本轮明确规格。 ## apinebula 审核例外（2026-11-05） 用户已明确允许 `apinebula` 第三方 GPT 审核替代本技能原来的官方审核要求。本节优先于后文及旧参考中的“仅官方”限制；DeepSeek、wokey 的成果也可交由独立 apinebula GPT 审核。可见成员接受 `modelProvider=apinebula`；隐藏审核及辅助池只接受实际核验的 `openai` 或 `apinebula`、`gpt-*` 模型及持久独立会话。记录保留真实提供方，apinebula 必须标为 `third_party`，不得称为 OpenAI 官方审核。提供方变化使原审核资格失效，不能跨提供方复用旧绑定。 沿用原配置、模型、认证和权限，不复制凭据。第三方额度保持未知，不查询官方账号或额度接口、不捏造百分比。独立性、准确候选摘要、必需测试和工具证据、暂停、未知结果不重放及审批规则保持不变。详见 [apinebula 接入与审核](references/apinebula.md)。 ## 成员与授权边界 已有任务恢复先核对原ID、执行和交付，不重新assign。新登记且必须原窗口执行的阶段使用assign --pin-member；独立核验使用--independent-of引用被核验任务。额度恢复不收回已转交任务，检查结果按准确版本记录，不沿用历史测试总数。 - 默认A/B两个用户已打开的原CLI；C/D使用本轮一次性邀请加入，最多四个可见成员。保留各自账号、提供方、模型、权限和原会话根cwd。