← ClaudeAtlas

codex-orchestratorlisted

Route bounded implementation work from Claude to Codex using Luna, Terra, and Sol profiles or an opt-in Sol-led subagent team. Use whenever Claude dispatches, resumes, reviews, or rescues Codex work, or when a Codex handoff is oversized, fails, or needs escalation.
vimoxshah/claude-codex-orchestrator · ★ 6 · AI & Automation · score 68
Install: claude install-skill vimoxshah/claude-codex-orchestrator
# Codex Orchestrator Workflow Keep planning, unresolved product and architecture decisions, integration, and the accepting verification verdict in Claude. Route execution to the narrowest capable Codex lane. ## Resolve the active policy Use `<repo>/CLAUDE-CODEX-ROUTING.md` when it exists; otherwise use `~/.claude/CLAUDE-CODEX-ROUTING.md`. Treat a repository policy as a wholesale override of the global policy. Keep the Claude-model router separate. `CLAUDE-CODEX-ROUTING.md` decides Claude versus Codex, the Claude router chooses a Claude tier, and this skill chooses a Codex lane. Fix overlapping ownership in the routing tables instead of arbitrating it per dispatch. ## Choose a dispatch mode Use one of two modes: 1. **Single bounded packet:** invoke the selected profile directly. Do not start a Sol coordinator merely to spawn one worker. 2. **Large frozen work order:** use `--profile orchestrated`. Its Sol root may decompose independent packets, route Luna to Terra to Sol, request `sol-reviewer`, and assemble the result. Claude still verifies the final diff in both modes. ## Resolve the direct profiles The ready-to-run files live in `codex-profiles/` and layer over the user's base Codex configuration. | Profile | Model and effort | Service tier | Use | | --- | --- | --- | --- | | `luna-worker` | `gpt-5.6-luna` max | default | Default executor for fully specified, deterministic work | | `luna-fast-worker` | `gpt-5.6-luna` max | fast | The same bounded work when latenc