Skip to main content
subagent CX Codex

dual-orchestrator — Claude Code subagent: routing and setup

dual-orchestrator routes work between interactive Claude Code and headless Codex: use one for reasoning and review, the other for parallel execution. Built for workflows that combine both.

no license ★ 850 updated 2026-10-26

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/agents/dual-orchestrator.md
Open on GitHub

What dual-orchestrator does

The subagent chooses a platform based on the task. Requests about architecture, debugging, and code review go to Claude Code; implementation, tests, documentation, and batch jobs go to Codex. Routing relies on wording patterns, so the prompt affects the choice.

A hybrid workflow can start with an architecture discussion in Claude Code, move into parallel implementation with Codex, then return to Claude Code for review. The setup also describes swarm coordination and shared memory for design decisions and worker results.

The examples launch background work with claude -p and retrieve results with npx claude-flow@v3alpha memory list --namespace results. Parallel Codex workflows therefore depend on those commands and the claude-flow integration; check them before using that flow.

What it helps with

  • split design and implementation across platforms
  • delegate several tasks for parallel execution
  • route debugging and code review to an interactive session
  • gather background task results for review

Example prompts for the agent

  • Plan the architecture for this feature, then assign the implementation to Codex as parallel tasks.
  • Investigate this bug in the existing code and explain where it originates.
  • Generate tests and documentation for this feature in background tasks, then bring the results back for review.

How to install dual-orchestrator

Manually: put the files in place

.claude/agents/dual-orchestrator.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about dual-orchestrator

How do I install dual-orchestrator in Claude Code?

Add the subagent file at .claude/agents/dual-orchestrator.md.

What does dual-orchestrator do?

It routes work between interactive Claude Code and headless Codex. Reasoning and review go to Claude Code, while parallel execution goes to Codex.

How does dual-orchestrator share design decisions with workers?

The workflow stores decisions in shared memory so workers can read them. Task results can be saved in the results namespace.

Similar subagents

All subagents for Agent setup: memory, context, orchestration →
Swarm Orchestration ruvnet Swarm Orchestration — a skill for managing agent swarms with parallel execution, dynamic topology, and automatic load balancing. Use when a single agent is not enough and you need to orchestrate specialists of different types. CX Codex +1 2,100installs do-in-parallel NeoLabHQ do-in-parallel runs isolated tasks across separate files concurrently via sub-agents and validates work with automated judges. Fits batch refactoring and doc generation. CX Codex +1 1,300installs dual-axis-skill-reviewer tradermonty dual-axis-skill-reviewer reviews skills with deterministic checks and an LLM axis, then combines both into one score. Use it to inspect quality before a merge or find concrete fixes. CX Codex +1 3,600installs multi-agent-coordinator rohitg00 multi-agent-coordinator decomposes complex tasks into parallel branches, resolves dependencies, and merges outputs from multiple agents into coherent deliverables. CX Codex ★ 2,858repo stars orchestrator Rohit Ghumare orchestrator — a subagent for Claude Code that splits complex builds into three phases: research, plan, implement. Each phase requires approval before the next — use it for features touching 5+ files or needing architecture decisions. CX Codex ★ 2,966repo stars gem-orchestrator official github gem-orchestrator is a GitHub Copilot subagent that coordinates planning, implementation, and verification across agents. It routes research, debugging, and discussion requests as well. CX Codex +1 ★ 41,430repo stars

From the same set76

The whole set →
commands The commands command for Claude Code is a reference for AI pair programming sessions, managing driver and navigator roles and running tests and code review from the terminal. CX Codex +1 ★ 850repo stars pseudocode Turns a finished spec into pseudocode: algorithms, data structures and a complexity estimate before any code is written. CX Codex ★ 850repo stars issue-tracker issue-tracker coordinates GitHub issue tracking with multi-agent swarms to structure bug reports, run progress updates, and sync project tasks. CX Codex +1 ★ 850repo stars tester tester — a subagent that designs and runs tests across the pyramid: units with mocks, integration against a real database, E2E flows, performance checks, and security validation. Keeps coverage above 80% and catches bugs early. CX Codex ★ 850repo stars goal-planner goal-planner — a GOAP planner subagent that turns a goal into an ordered set of actions and reworks the plan when a step fails. CX Codex ★ 850repo stars v3-memory-specialist The v3-memory-specialist subagent for Claude Code migrates scattered project memory into AgentDB with HNSW indexing, speeding semantic search and sharing context across agents. CX Codex ★ 850repo stars config Loads a reference for pair programming settings: driver, navigator and switch modes, verification thresholds, test runs and agent profiles kept in .claude-flow/pair-config.json. CX Codex +1 ★ 850repo stars workflow-automation workflow-automation integrates multi-agent swarms with GitHub Actions pipelines to generate CI configurations, select tests, and inspect build failures. CX Codex +1 ★ 850repo stars

Project sponsors

Companies that keep this analytics open