Cc Codex Flow

• Role: Orchestrator, planner, validator

Codex Environment

• Model: Configured in ~/.codex/config.toml
• Proxy: Required for OpenAI API access (configure during installation)
• MCP Configuration in ~/.claude.json:

{
  "mcpServers": {
    "codex": {
      "type": "stdio",
      "command": "codex",
      "args": ["mcp-server"],
      "env": {
        "HTTP_PROXY": "http://127.0.0.1:7897",
        "HTTPS_PROXY": "http://127.0.0.1:7897",
        "NO_PROXY": "localhost,127.0.0.1"
      }
    }
  }
}

Workflow

Phase 1: Information Collection (Claude Code)

Gather context using available tools:

• WebSearch: Latest documentation and best practices
• Glob/Grep: Analyze existing code structure
• Read: Understand current implementation

Output: Context report covering tech stack, relevant files, patterns, and potential risks.

Phase 2: Task Planning

Create a structured plan using this template:

## Tech Spec
Goal: [Single sentence objective]
Tech: [Language/framework/libraries]
Risks: [Potential breaking changes]
Compatibility: [How to preserve existing behavior]

## Tasks
- [ ] Task 1: [Description]
  - Executor: Codex
  - Files: [Paths]
  - Constraints: [Limitations]
  - Acceptance: [Verification criteria]

Phase 3: Execution (Codex-First)

Delegate code tasks to Codex via MCP:

mcp__codex__codex({
  "sandbox": "danger-full-access",
  "approval-policy": "on-failure",
  "prompt": "<structured prompt with context, task, constraints, acceptance criteria>"
})

Session Management:

• Capture threadId from the response
• Use mcp__codex__codex-reply for follow-up messages:

  mcp__codex__codex-reply({
    "threadId": "<saved-thread-id>",
    "prompt": "<next instruction>"
  })
  

Phase 4: Validation (Claude Code)

Verify the implementation:

• Functionality works as expected
• Tests pass (if applicable)
• No type errors
• Performance acceptable
• No API breakage
• Code style consistent

If issues found, return to Phase 3 with specific fixes.

Routing Matrix

Codex Prompt Template

When calling Codex, use this structure:

## Context
- Tech Stack: [language/framework/version]
- Files: [path]: [purpose]
- Reference: [file for pattern/style]

## Task
[Clear, specific, verifiable task]

Steps:
1. [First step]
2. [Second step]
3. [Third step]

## Constraints
- API: Don't change [signatures]
- Performance: [requirements]
- Style: Follow [reference file]
- Scope: Only modify [specified files]
- Dependencies: No new deps without approval

## Acceptance Criteria
- [ ] Tests pass
- [ ] Types compile
- [ ] Linter clean
- [ ] [Project-specific criteria]

Anti-Patterns

Success Metrics

• Efficiency: >80% first-time success rate
• Quality: Zero API breakage, maintained test coverage
• Speed: <5 min average task completion

Examples

Simple Task

/cc-codex-flow Add email validation to the user registration form

Complex Task

/cc-codex-flow Implement user authentication with JWT, including login, registration, password reset, and session management

Refactoring Task

/cc-codex-flow Refactor the payment processing module to use the strategy pattern for multiple payment providers