Last verified 16 August 2026
HRA vs Superset
Both organize parallel agent work around isolated Git worktrees, local hosts, durable task state, and human review.1346789
Short answer
Choose for the job in front of you.
Choose Superset
Choose Superset when you want a programmable workspace platform, broad agent support, automations, and control through desktop, CLI, SDK, or MCP.6789
Choose HRA
Choose HRA when the system can be Codex-only and the primary need is coordinated authorized accounts, recursive task ownership, continuity, and fail-closed recovery.134
The meaningful difference
The products put authority in different places.
Superset is a broad source-available coding platform exposed as a desktop IDE, CLI, SDK, and MCP server. HRA is a smaller Codex-specific control system that makes account generations, actor lineage, model intent, and recovery evidence part of the durable record.1346789
Side by side
The decisions that matter.
| Decision | HRA | Superset |
|---|---|---|
| Core job | A durable metaharness around Codex.13 | A source-available AI coding platform for tasks, workspaces, agents, and automations.69 |
| Interfaces | Native Mac host plus a bounded web control plane.24 | Desktop IDE, CLI, SDK, and MCP server.689 |
| Agent scope | Codex actors with fixed work classes and inherited authority.35 | Claude Code, Cursor, Codex, and other terminal agents in workspaces.7 |
| Automation | Recursive delegation inside a durable Codex task graph.13 | Tasks, automations, workspace APIs, and programmatic agent creation.89 |
| Account custody | Separate authorized Codex identities and generations are part of admission and recovery.24 | Host and workspace orchestration; HRA-style multi-Codex identity custody is not its documented center.6 |
| Best fit | Codex-specific correctness and recovery depth.13 | A broad programmable platform for agent workspaces and operations.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 ↗
- Superset documentation: Overview ↗
- Superset documentation: AI agents ↗
- Superset documentation: CLI reference ↗
- Superset documentation: MCP server ↗
“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 Superset. Report a correction.