Codex Collaboration

Coordinate Claude Code and Codex CLI workflows with configurable lead patterns.

3|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/masuP9/codex-collab --skill codex-collaboration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Codex Collaboration
Source: https://github.com/masuP9/codex-collab/tree/main/skills/codex-collaboration
Command: npx skills add https://github.com/masuP9/codex-collab --skill codex-collaboration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill orchestrates collaboration between Claude Code and the OpenAI Codex CLI to enable end-to-end task planning, implementation, and review with clear handoffs and guardrails.

Core Features & Use Cases

  • Codex-led planning and review; Claude Code handles implementation, testing, and file operations
  • Claude-led planning with fast Codex implementation in a workspace-write sandbox
  • Default Codex-Leads workflow, with an explicit option to switch to claude-leads, and configurable prerequisites and settings
  • Project-level and per-task configuration via .claude/codex-collab.local.* files, plus optional resources under scripts/ and references/

Quick Start

Ask Claude Code and Codex to plan, implement, and review a feature end-to-end using the default Codex-Leads workflow.

Frequently Asked Questions about Codex Collaboration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate Claude Code and Codex CLI for collaborative task planning?

Coordinate Claude Code and Codex CLI by selecting workflow modes based on model strengths. The default Codex-Leads pattern assigns planning and review to Codex while Claude Code handles implementation and file operations.

What is the best way to use Codex for code review with Claude Code for implementation?

Use the Codex-Leads workflow to let Codex drive planning and code review, while Claude Code executes implementation, testing, and file operations. This division leverages each model's strengths for end-to-end task completion.

Can I switch to a Claude-led planning workflow with Codex implementation?

Yes, you can switch to the Claude-Leads workflow. This pattern lets Claude Code handle planning while Codex executes fast implementation within a workspace-write sandbox environment.

Do I need local configuration files to run Codex and Claude Code collaboration?

Yes, local configuration is required. You must set up project-level and per-task settings using .claude/codex-collab.local.* files to define prerequisites and configurable settings for the collaboration.

Why does Codex need stateless invocations during Claude Code collaboration?

Codex requires stateless invocations enforced via codex exec to ensure deterministic execution. This prevents state drift between planning, implementation, and review phases across the collaboration workflow.

What limitations exist when orchestrating Claude Code and Codex CLI workflows?

Limitations include mandatory local configuration via .claude files and reliance on stateless codex exec calls. Optional planning and review resources under scripts and references directories are also required for full functionality.