Last verified 16 August 2026
HRA vs Conductor
Both help a developer run several coding-agent tasks without colliding in one checkout and bring the changes back through review.134678
Short answer
Choose for the job in front of you.
Choose Conductor
Choose Conductor for a mature Mac workspace, diff, checks, and pull-request workflow across Codex, Claude Code, Cursor, and OpenCode.678
Choose HRA
Choose HRA when work must form one persistent Codex task graph and recover across multiple authorized Codex identities, not merely land as parallel branches.134
The meaningful difference
The products put authority in different places.
Conductor makes each task a polished workspace with its own branch, files, terminal, diff, checks, and pull-request path across several harnesses. HRA focuses on the coordination semantics inside one Codex workload: account custody, recursive delegation, continuity, and recovery evidence.134678
Side by side
The decisions that matter.
| Decision | HRA | Conductor |
|---|---|---|
| Core job | Coordinate one durable Codex workload.13 | Create isolated agent workspaces and carry each through review and merge.6 |
| Harnesses | Codex only by design.23 | Codex, Claude Code, Cursor, and OpenCode.6 |
| Isolation | Managed worktrees owned by durable actors and task claims.34 | A workspace, branch, files, terminal, diff, and review path per independent task.78 |
| Coordination | Parent-child tasks, dependencies, inherited authority, submissions, and review.13 | Parallel workspaces or multiple sessions inside one shared workspace.7 |
| Account identities | Multiple authorized Codex identities are routed separately.24 | Uses Codex access in its workspaces; multi-identity Codex routing is not its documented center.8 |
| Best fit | Codex-specific durable orchestration.13 | Polished workspace isolation and change review across popular coding agents.6 |
What HRA cannot do yet
Current HRA limitations.
- HRA's native host currently supports Apple Silicon Macs only.
- The downloadable app is ad-hoc signed, not Developer ID signed or notarized.
- The recursive harness is experimental, and the adaptive optimizer cannot activate policy.
- HRA is Codex-only; it is the wrong choice when provider breadth is the requirement.
- Multiple accounts must be owned or authorized by you and permitted to access the same work.
How we verified this
Current first-party sources.
- HRA v0.1.7: Project overview ↗
- HRA v0.1.7: macOS architecture and limits ↗
- HRA v0.1.7: Recursive Codex harness ↗
- HRA v0.1.7: Security architecture ↗
- HRA v0.1.7: Model and acceleration policy ↗
- Conductor documentation: Introduction ↗
- Conductor documentation: Parallel agents ↗
- Conductor documentation: Multiple Codex sessions ↗
“Not documented” means only that a capability was not found in these sources on 16 August 2026. It does not prove the product lacks it. HRA is independent and unaffiliated with Conductor. Report a correction.