Hebra gives every coding agent its own workspace, warns when two of them touch the same file, and records who asked for each change. It speaks Git, and it has its own server and web.
Git was built for people taking turns. Hebra keeps agents apart while they work and brings their work together under review. Everything below is live, so press it.
$ hb start "add OAuth login" --agent claude-codeStarted workspace add-oauth-loginchange: rysttrtz base: a6d6307d777f$ hb start "rate limit login" --agent codexStarted workspace rate-limit-login
hb start makes an isolated workspace with a fresh change. Nothing an agent does touches your files or another agent's.
Agents claim what they are about to change. When two reach for the same file, both hear about it, in the CLI, over MCP and in the hub.
<<<<<<< ours
let limit = oauth::limit(&user);
=======
let limit = 100;
>>>>>>> theirsConflicts are saved inside the change, and work goes on. A person or another agent settles them when ready.
hb reset --hard @--
2 changes dropped, still here
Drag it back. hb undo takes back anything, including reset --hard, and hb op restore goes to any point.
claude-code
agent for ana
rysttrtzs_9f2c41Person, agent, task, session and prompt stay in history, and travel to Git as trailers when you export.
Mandate for claude-code
Expires in 8 hours
agents/claude-code/*A credential narrowed offline to one repository, a few operations and its own bookmarks. It expires, and revoking yours revokes it.
Each workspace reports what it is editing and claiming. The pill turns rose when two touch the same file. Press it.
Who did the work, and the conflicts under the line. This one is example data. The hub draws yours.
$ hb status --json{ "changes": [{ "path": "src/auth.rs", "status": "modified" }], "conflicts": [],"warnings": { "overlapping": ["src/auth.rs"] } }
--json on every command, stable error codes, and hb mcp for any MCP client. Nothing ever waits for a keypress.
hb covers every command in git help -a, and a test checks that list against the installed Git. Clone, fetch and push work against any Git remote, and commits that came from Git keep their SHA. See every command
| What | Git | Hebra |
|---|---|---|
| Several agents at once | Worktrees and branches by hand | hb start: one workspace each |
| Two agents on one file | Found at merge time | Warned while they work |
| Conflicts | Stop the merge | Saved in the change; work goes on |
| Who changed what | Name and email | Person, agent, task, session, prompt |
| Credentials for agents | Your token, all of it | A narrowed, expiring mandate |
| Commands at the same time | Fail on index.lock | Run side by side and merge their results |
| Staging area | An index to manage | None: the working copy is the change |
| Undo | Depends on the command | Every operation, files included |
| Interface for agents | Parse human output | --json everywhere and MCP |
It skips checks whose inputs did not change, and starts and stops machines at your cloud provider for the rest. Watch one push.
1.39
machine cost, cheap goal
A team's week: 2.75 with a 5-minute autoscaler, 1.53 with one machine per job
0 s
median wait
Same week: 22 s with the autoscaler, 25 s with a machine per job
~3×
less, counting time
Balanced goal: machines plus the hours people wait, 2.7× to 3.4× lower on team, agent and steady loads
Your API token, your goal, your limit. Every start and stop is logged with its reason.
Numbers from hb heddle simulate on made-up workloads and an example price list, 4 November 2026. Run it with your own prices.
npm and Docker talk to it with their own commands. Releases carry the files a build makes, and webhooks tell other systems what happened.
Steps, a matrix, checks that wait for others, containers with services, secrets masked in logs, artifacts, caches and retries. An environment adds approvals and its own runners and secrets.
[[check]]
name = "test"
matrix = { os = ["linux", "windows"] }
labels = ["${{ matrix.os }}"]
run = "cargo test"
inputs = ["crates/**", "Cargo.lock"]
[[check]]
name = "deploy"
needs = ["test"]
environment = "production"
secrets = ["DEPLOY_KEY"]
run = "./deploy.sh"Make a token in the hub and run this on the machine. It registers itself and installs a service, so it comes back after reboots. Nobody signs in on it.
$ npm publish
+ @acme/ui@1.4.0
$ npm dist-tag add @acme/ui@1.4.0 stable
+stable: @acme/ui@1.4.0
Packages scoped by an account (@acme/ui). npm publish, install, dist-tag and unpublish, with a mandate in .npmrc.
$ docker push hebra.example.com/acme/app:1.0
1.0: digest: sha256:4f1c9e… size: 1573
$ docker pull hebra.example.com/acme/app:1.0
Status: Downloaded newer image
The OCI distribution API: docker login with a mandate, then push and pull. Multi-platform images and shared layers are kept once.
v1.4.0 Faster clones
hb-x86_64-linux.tar.gz 6.1 MB
hb-aarch64-macos.tar.gz 5.8 MB
SHA256SUMS 220 B
A pushed tag with notes and the files a build made. Checks upload them with one curl; downloads are counted.
POST https://ci.example.com/hebra
X-Hebra-Event: release
X-Hebra-Signature-256: sha256=9b1e…
200 in 84 ms
Pushes, reviews, tasks, checks and releases POSTed as JSON, signed with HMAC-SHA256. Failed ones are tried three times, and every try is kept.
runs-on: ubuntu-latest → linux
${{ secrets.TOKEN }} → $TOKEN
actions/cache@v4 → cache
actions/upload-artifact@v4 → artifacts
A repository without .hb/checks.toml runs .github/workflows as they are: jobs, needs, matrix, containers, services, secrets.
$ hb search retry webhook delivery
crates/server/src/webhooks.rs:41-80 deliver
pub(crate) async fn deliver(s: &Server, …
Changes 9b17d21c9ee6 feat: releases and signed webhooks
hb search ranks functions, types and sections by the words of the question, and the changes whose reason matches. Nothing to download.
Measured on one desktop PC on 2 November 2026, with scripts/stress.sh and crates/load from the repository. Run them on yours.
Install the CLI, start in a project, and give two agents a workspace each. It takes about a minute.
1Install hb
2Start in a project, or clone one from Git
3Give an agent its own workspace
4Let your agent use it
Prefer a binary? Download hb for macOS, Linux or Windows from the releases page, with checksums and signed provenance.
The whole server and this web on your hardware, Apache 2.0. One binary with SQLite, or Docker Compose and Kubernetes with Postgres, S3 and NATS.
Self-hosting guide