Last verified 16 August 2026
HRA vs OpenCode Desktop
Both are open-source desktop tools for agent and subagent work in local repositories, with a human-facing session interface.1346789
Short answer
Choose for the job in front of you.
Choose OpenCode Desktop
Choose OpenCode Desktop when provider and model freedom, cross-platform support, configurable agents, and one open agent runtime matter most.6789
Choose HRA
Choose HRA when you want official Codex sessions underneath a persistent task graph with account isolation, work-class routing, review, and generation-fenced recovery.134
The meaningful difference
The products put authority in different places.
OpenCode Desktop is an interface for an agent runtime that lets you choose providers, models, permissions, and agent definitions. HRA keeps Codex as the runtime and specializes in coordinating a durable workload across several authorized Codex identities.1346789
Side by side
The decisions that matter.
| Decision | HRA | OpenCode Desktop |
|---|---|---|
| Core job | Operate a durable coordination layer around Codex.13 | Run an open coding agent across many model providers.68 |
| Platforms | Apple Silicon macOS prerelease.2 | Terminal, desktop, and IDE surfaces; desktop builds cover macOS, Windows, and Linux.9 |
| Agents | Persistent Codex actors with bounded parent-child authority.34 | Configurable primary agents and subagents with model, prompt, permissions, and tool access.7 |
| Provider scope | Codex only by design.23 | Many providers and models, including OpenAI-compatible options.8 |
| Account coordination | Separate authorized Codex identities are first-class routing inputs.24 | Provider authentication is documented; HRA-style multi-Codex identity scheduling is not the product focus.8 |
| Best fit | Codex-specific orchestration, continuity, and recovery.13 | An open, configurable coding-agent runtime with broad provider choice.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 ↗
- OpenCode documentation: Introduction ↗
- OpenCode documentation: Agents ↗
- OpenCode documentation: Providers ↗
- OpenCode source and desktop downloads ↗
“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 OpenCode Desktop. Report a correction.