Last verified 16 August 2026
HRA vs Paseo
Both go beyond a chat grid: they manage worktrees, sessions, follow-ups, model choices, subagents, and long-running work from a control surface.1346789
Short answer
Choose for the job in front of you.
Choose Paseo
Choose Paseo for cross-provider orchestration, multiple provider profiles, remote access, mobile supervision, schedules, and a mature workspace CLI.6789
Choose HRA
Choose HRA when all workers are Codex and the hard problem is exact account isolation, durable delegation, continuity, and fail-closed recovery rather than provider breadth.134
The meaningful difference
The products put authority in different places.
Paseo emphasizes provider breadth and access across desktop, web, mobile, and CLI. HRA is narrower: it treats Codex account custody, work-class routing, durable parent-child work, and recovery receipts as one Codex-specific system.1346789
Side by side
The decisions that matter.
| Decision | HRA | Paseo |
|---|---|---|
| Core job | A Codex metaharness with durable task and effect custody.13 | A cross-provider agent orchestrator available across several surfaces.69 |
| Provider scope | Codex only by design.23 | First-class and custom providers, including multiple profiles for one provider.7 |
| Parallel work | Managed worktrees plus a persistent parent-child task graph.14 | Worktree workspaces and orchestrated child sessions.86 |
| Devices | Native execution on an Apple Silicon Mac with a bounded hosted view.24 | Desktop, web, mobile, and CLI around a daemon.9 |
| Recovery emphasis | Provider generations, effect receipts, ambiguity containment, and exact account leases.34 | Daemon-owned sessions, heartbeats, follow-ups, and orchestration lifecycle.6 |
| Best fit | A deep Codex-only control system.13 | A broad agent command center across providers and devices.9 |
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 ↗
- Paseo documentation: Orchestration ↗
- Paseo documentation: Custom providers ↗
- Paseo documentation: Git worktrees ↗
- Paseo source ↗
“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 Paseo. Report a correction.