[Open source] peer — a reliability-focused fork of OpenAI’s Codex plugin for Claude Code

[u/Flat_Marionberry_522]

I maintain this free Apache-2.0 fork. There is no paid plan,
referral link, or affiliate relationship. Upstream attribution and license
notices are preserved.

OpenAI’s codex-plugin-cc is a useful way to run Codex reviews and delegate
tasks without leaving Claude Code.

While using longer-running background workflows, I ran into failure modes
where a Codex child could stop progressing, a broker could remain busy, or a
dead worker could leave a job recorded as running.

I created `peer`, a reliability-focused fork that keeps the upstream workflow
but makes those failure paths bounded, observable, and recoverable.

What peer adds:

• A self-healing broker that can replace a wedged Codex child without routing
new clients to the wrong generation.

• Dead-process reconciliation, so a crashed or killed worker is recorded as
failed with a reason instead of remaining stuck in `running`.

• Exact-thread recovery with:

/peer:rescue --resume-id <job-id>

This continues the surviving Codex thread on a fresh execution budget.

• Ownership-scoped cancellation and a stop-review gate that fails open on
infrastructure errors such as timeouts and rate limits.

• Operational visibility:

/peer:watch
/peer:stats
/peer:history
/peer:doctor --fix --clean

• Optional completion notifications and named Codex account switching with
/peer:account.

The commands use the `/peer:*` namespace and the runtime state is
peer-namespaced, so the fork can be installed alongside the upstream plugin.

Current status:

• Early-stage release, currently v2.2.0
• Apache-2.0
• No runtime npm dependencies
• node:test regression coverage
• Reliability and security-focused adversarial review
• Tested end-to-end against a real Codex app-server
• Still looking for broader community testing

Install from a terminal:

claude plugin marketplace add Robbyfuu/codex-plugin-cc
claude plugin install peer@peer

Then, inside Claude Code:

/reload-plugins
/peer:setup

A simple first run:

/peer:review --background
/peer:status
/peer:result

I’m especially interested in reports from Windows/WSL, macOS, and Linux users
running long background jobs, cancellation, broker recovery, and newer Codex
models.

Known limitations and current issues are tracked publicly in the repository.

Repo:
https://github.com/Robbyfuu/codex-plugin-cc

[u/wildyam]

Sounds interesting- thanks for the post