This site and repository preserve the original HRA macOS metaharness, its source, and its final v0.1.14 prerelease.
The current HRA is a separate project. New users should start at hra.sh or read its current source. Existing v0 users can keep using the archive and download below.
Parallel sessions become a system only when they can divide work and meet again.
One durable outcome
Plan
Review
↓ delegate · route · recover ↓
Coordinated Codex work
Root sessions
Bounded children
The task graph outlives any one agent window.
Why HRA exists
Parallel is the beginning, not the product.
A row of sessions can do more work. It cannot decide which work belongs together, preserve ownership after a restart, or tell a bounded helper how to return to its parent. HRA supplies that missing layer.
01
Coordinate the accounts you already use
Pair separate Codex accounts that you own or are authorized to use. Credentials and provider sessions remain isolated on your Mac.
02
Delegate work with structure
Turn one outcome into durable parent and child tasks with dependencies, bounded ownership, and an explicit path back to review.
03
Spend reasoning deliberately
Give wide work more room, bounded work a lighter lane, and follow-ups the same conversation when continuity is still safe.
04
Recover the work, not just the window
Persist who owned each effect, what was observed, and what still needs review so a restart does not turn uncertainty into a duplicate action.
How it works
Describe the outcome once. Keep the coordination outside the prompt.
01
Connect the Mac
Choose the repositories and Codex accounts this installation is allowed to use.
02
Describe the outcome
HRA keeps the plan, dependencies, ownership, and review state outside any one agent conversation.
03
Let the work divide
Codex sessions run in managed worktrees; bounded child work can proceed in parallel without becoming unrelated tabs.
04
Review and continue
Accept the result, answer a question, redirect a branch, or resume the same durable task after an interruption.
The honest fit
HRA is intentionally narrower than an AI IDE.
It goes deep on Codex orchestration. If your main problem is provider choice, remote access, or isolated worktrees, another tool may be the more direct answer.
Use HRA when
one project needs several coordinated Codex sessions
you have separate authorized Codex accounts to keep isolated
child work must rejoin a durable parent task
restarts and ambiguous effects need explicit recovery
Choose something simpler when
you want the first-party Codex experience for a few independent sessions
your team needs one desktop for many model providers
the main problem is remote access from a phone
a worktree launcher and diff viewer already solve the job
HRA keeps repositories, commands, credentials, raw transcripts, and provider sessions on the paired Mac. The hosted surface sees bounded coordination and review state.
A harness runs an agent. A metaharness decides how several harnesses divide work, share bounded context, choose a lane, recover interrupted effects, and bring results back to one review path. Codex does the coding; HRA coordinates the system around it.
Does HRA bypass Codex limits?
No. A provider limit ends the affected turn. HRA does not move that work to another account. Every account remains subject to its own plan, limits, organization policy, and OpenAI terms. Use only accounts you own or are authorized to use, and group them only when each is allowed to access the same repository and data.
How is this different from the Codex app?
The Codex app is the first-party place to run and review parallel Codex sessions. HRA is for the layer above them: several isolated account identities, a durable parent-and-child task graph, work-aware routing, human gates, and crash recovery across sessions.
Where does execution authority live?
On the paired Mac. Provider credentials, local repositories, commands, raw transcripts, and provider session identifiers do not become browser authority. The hosted surface receives bounded coordination and review state.
What can I install today?
An Apple Silicon macOS prerelease. It is ad-hoc signed for bundle integrity but is not Developer ID signed or notarized, so macOS will identify it as coming from an unknown developer. The download page explains that limitation before installation.
Open source
The harness should be inspectable.
The public repository includes the product source, security architecture, build checks, and the exact boundaries around local execution.
