orchestrator · devin-axis — Claude Code subagent: what it does, how to install
orchestrator plans implementation steps, breaks down tasks, and validates test runs while delegating all coding to an executor agent. Helpful for rigorous quality workflows.
LicenseRef-Proprietary ★ 7,523 updated 2026-10-29
.claude/agents/orchestrator.mdWhat orchestrator does
The agent acts as a lead coordinator powered by anthropic/claude-fable-5. It inspects repository structure, breaks features into clear task briefs with acceptance criteria, and intentionally avoids writing code directly. All file modifications, bug fixes, and feature builds are handed off to the executor subagent running GPT 5.5 via the Task tool.
Once the executor reports back, orchestrator runs an independent review. It audits diffs, triggers typechecks, runs builds, and verifies UI flows using fraimz. If validation fails, it routes the task back with explicit repair steps. Without the companion executor agent configured, this subagent cannot complete work because it refuses to modify source files on its own.
The paved path follows demo-driven development documented in AGENTS.md. Work happens inside an isolated worktree created with git worktree add, while pull requests require verification proof generated by pnpm fraimz --flow <id> --pr.
What it helps with
- break down complex features into explicit task briefs with acceptance criteria
- delegate file edits and bug fixes to the executor subagent
- verify git diffs, builds, and test suites before finishing a task
- validate user flows and UI frames using fraimz
Example prompts for the agent
- Plan the OAuth integration steps and assign tasks to executor
- Review the recent diff from executor and run the test suite
- Set up a fresh worktree and prepare the demo flow according to AGENTS.md
How to install orchestrator
Manually: put the files in place
.claude/agents/orchestrator.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/orchestrator.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/orchestrator.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about orchestrator
How do I install orchestrator in Claude Code?
Create the subagent configuration file at .claude/agents/orchestrator.md. In Codex, place the file at .codex/agents/orchestrator.toml.
What does the orchestrator subagent do?
It manages project planning, delegates programming tasks to the executor subagent, and verifies all resulting code. It inspects diffs, runs test suites, and validates application flows before marking work complete.
Why does orchestrator avoid writing code directly?
The workflow separates high-level planning from code generation. The orchestrator focuses strictly on task design and output verification, leaving file changes to the GPT 5.5 executor.
Similar subagents
All subagents for Agent setup: memory, context, orchestration →orchestrator by other authors comes first.