codex-collab

Solid

Use when the user asks to invoke, delegate to, or collaborate with Codex on any task. Also use PROACTIVELY when an independent, non-Claude perspective from Codex would add value — second opinions on code, plans, architecture, or design decisions.

Web & Frontend 93 stars 8 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
66
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# codex-collab codex-collab is a bridge between Claude and Codex. It communicates with Codex via the `codex app-server` JSON-RPC protocol, giving you structured, event-driven access to Codex's capabilities — prompting, code review, tool use, and file editing. Requires bun and the codex CLI on PATH (`codex-collab health` to verify). ## Run Command (Recommended for Prompted Tasks) The `run` command handles prompted tasks in one call: starts a thread, sends the prompt, waits for the turn to complete, and prints output. ```bash # Research task codex-collab run "what does this project do?" -s read-only --content-only # Implementation task codex-collab run "add input validation to the login form" --content-only # Resume an existing thread (preserves conversation context) codex-collab run --resume <id> "now check the error handling" --content-only # Specify working directory (omit -d if already in the project dir) codex-collab run "investigate the auth module" -d /path/to/project --content-only # Long or quote-riddled prompt: pass it on stdin with `run -` (no shell-quoting hazards) cat prompt.md | codex-collab run - --content-only ``` **IMPORTANT — Execution rules for ALL `codex-collab` Bash commands:** - Always use `dangerouslyDisableSandbox=true` — the tool writes to `~/.codex-collab/` which is outside the sandbox allowlist. - For `run` and `review`: also use `run_in_background=true` — these take minutes. After launching, tell the user it's running and end your turn. **Wh...

Details

Author
Kevin7Qi
Repository
Kevin7Qi/codex-collab
Created
5 months ago
Last Updated
1 weeks ago
Language
TypeScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

codex-collab

Ask Codex CLI for an explicitly requested, read-only second opinion on a bounded review, diagnosis, architecture, or comparison question.

2 Updated today
rocky2431
AI & Automation Solid

codex

Use the local Codex CLI as an independent second agent. Two branches — (1) proactively run `codex review` for a second opinion after completing a substantive change, before presenting it as done or committing; (2) delegate a well-defined implementation task via `codex exec`, ONLY when the user explicitly asks for Codex to do it. Also covers how to prompt Codex.

41 Updated 2 days ago
dzhng
Code & Development Listed

using-codex-collaboration

Use proactively whenever the work involves substantial code changes (multi-file, core logic, architecture), a freshly written execution plan, a sticky bug that resists single-perspective diagnosis, or a non-obvious design decision that needs adversarial challenge — establishes when and how to bring Codex in as a reviewer (not as an executor). The ONLY channel is the persistent Codex pane reached via tmux (send-keys / capture-pane) — this holds even when Claude's own session is NOT running inside tmux (drive the tmux server externally; create a detached session if needed). Direct `codex` CLI invocation (codex exec etc.) is FORBIDDEN unless the user explicitly requests it, because it loses context. Covers locating/launching the Codex pane, the predefined collaboration scenarios (review-uncommitted, plan review, adversarial challenge, bug rescue), and the review⇄fix consensus loop that runs until Codex passes.

0 Updated 1 weeks ago
Jewel591