Last verified 16 August 2026
HRA vs Codex app
Both run Codex locally, support parallel work, preserve conversation context, and give a human a place to inspect results.1346789
Short answer
Choose for the job in front of you.
Choose Codex app
Choose Codex app for the supported first-party experience, built-in worktrees and subagents, skills, automations, and the shortest path from prompt to parallel Codex work.6789
Choose HRA
Choose HRA when several Codex sessions must behave like one recoverable project and you need explicit account isolation, delegation, dependencies, review gates, and cross-session recovery.134
The meaningful difference
The products put authority in different places.
Codex app is the first-party Codex experience. HRA deliberately sits one level above Codex sessions: it coordinates separate authorized account identities, models parent and child work durably, and records enough effect evidence to recover without guessing after a crash.1346789
Side by side
The decisions that matter.
| Decision | HRA | Codex app |
|---|---|---|
| Core job | Coordinate a durable Codex workload across sessions.13 | Provide the first-party interface for running and reviewing Codex.6 |
| Parallel work | Managed roots and bounded child work in a persistent task graph.14 | Parallel chats, isolated worktrees, and native subagents.78 |
| Account identities | Several authorized Codex accounts can be paired with separate local custody.24 | Codex desktop does not currently support ChatGPT account switching.9 |
| Coordination state | Dependencies, claims, leases, submissions, questions, and review survive sessions.14 | Projects, threads, skills, automations, and long-running work live in the first-party product.6 |
| Recovery | Generation-bound receipts reconcile applied, absent, ambiguous, and rerouted effects.34 | Thread continuity and app-managed task state; HRA's receipt graph is a different layer.6 |
| Best fit | A Codex-only system whose coordination must outlive any one session.13 | Most people starting with parallel Codex work or wanting first-party support.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 ↗
- OpenAI: Introducing the Codex app ↗
- Codex documentation: Git worktrees ↗
- Codex documentation: Subagents ↗
- OpenAI Help: Use multiple accounts ↗
“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 OpenAI Codex app. Report a correction.