HRA
Open HRA

Workspace for Codex and Claude Code

HRA

All your agents. One place to keep up.

See what’s running, follow the conversation, and decide what happens next. HRA brings your Codex and Claude Code sessions together in a web workspace, with a CLI for you and your agents.

Your machines run the work. HRA keeps you in the conversation.

Open HRAGet started

Public beta · Codex on macOS and Linux · Claude Code on Linux

New machine setup is temporarily paused. Check current availability →

Follow several sessions at once. Each card keeps its state, recent work, and next action together.

Real HRA interface, fictional sessions and accounts. These examples cannot sign in, send a request, or change a machine.Read the guide ↗

Loading the example interface…

Screen controls need JavaScript. The written guides cover each workflow.

HRA · Session grid

Real HRA interface, fictional sessions and accounts. These examples cannot sign in, send a request, or change a machine.

See the whole workspace
A grid of sessions shows what is running and what needs your attention. Open a card to read the conversation.
Pick up the next turn
Send a follow-up from the browser or terminal. The session runs on its machine, even after you close the tab.
Keep accounts separate
Choose the provider profile for the work. Each managed profile has its own configuration; HRA does not rotate accounts for you.

How it works

The same work, from your terminal.

Use the web workspace when you want to see the work. Use the CLI when you want to script it. Both address the same sessions.

These commands run on an initialized, authorized machine. Complete setup first.

  1. Starthra session start personal --provider codex --json

    Create a Codex session under the account profile you choose.

  2. Inspecthra session status <session-id> --json

    Read the session and the cursor where its event stream continues.

  3. Switchhra session switch <session-id> --provider claude --preset fable-max

    Continue on your signed-in Claude Code profile. HRA carries over the conversation it has retained and flags any missing history.

  4. Directhra session send <session-id> -- "Review this project."

    Send the next request to that session and provider.

Local by design

Your workspace. Your machines.

The browser gives you a view of the work. Execution stays with the provider tools on the machine you chose.

Your accounts, your provider tools
Codex and Claude Code own their sign-in and execution. HRA keeps managed profiles separate and does not broker model access.
Local by default
The local daemon runs the sessions. The CLI works without an HRA cloud identity; optional sync connects the web workspace and your other devices.
Encrypted before it leaves the machine
Synced session content is encrypted for paired devices. The service still sees account and delivery metadata, described in the privacy policy.
Analytics you can audit
hra.sh counts page views anonymously, without cookies, only on the production host, and honors Do Not Track. The privacy page lists every field.

Questions

A few things to know.

Does HRA need an account?

The local CLI does not need an HRA cloud identity. The web workspace does: sign in, pair your machine, and enroll the browser so it can decrypt your synced sessions. Your Codex and Claude Code accounts are separate.

Can I start using it now?

The website, web app, and hosted sync are available in open beta. The admitted v0.7.1 CLI has its own immutable install instructions. Starting or upgrading a daemon and enabling hosted commands are paused until the capacity checks pass. Check the setup status before starting a daemon.

Does HRA use my API keys or provider subscription?

HRA does not broker model access. Each provider CLI keeps using its own account, billing, and terms. HRA adds isolation, durability, and one command surface on top.

How do agents drive it?

The CLI exposes structured JSON and a cursor-based event stream. An agent can start a session, inspect its status, send a request, and follow progress. Read the command reference for the exact interface.

What if the terminal closes?

A session can outlive the terminal or browser tab because the local daemon owns its process. If the daemon itself stops, recovery depends on proving the old process is no longer writing. See session recovery before restarting uncertain work.

Which platforms are supported?

The CLI requires Bun 1.3.14. Codex execution supports macOS and Linux; Claude Code execution supports Linux. The web interface can follow paired machines from a browser. ChatGPT desktop account switching is macOS-only.

Built by

Built by Ben Guo

HRA is built by Ben Guo, a musician and builder, formerly a founder and engineering leader at companies including Venmo and Stripe, who now builds his software factory from Puerto Rico. He runs more than a dozen Codex subscriptions at once and built HRA to keep every session alive, isolated, and reachable from the same terminal.

Keep the work in view.

Start with one machine and one provider account. The setup guide explains what is available now and walks you through each step.

Set up your first machineOpen HRA

Public beta · Codex on macOS and Linux · Claude Code on Linux

Looking for the former reference?

The same command and safety reference now lives in the documentation.