For people who run more than one coding agent

Hivelane

Air traffic control for your coding agents. The agent you talk to stays in charge. Hivelane sends each task to the agent that fits it, keeps them out of each other's files, and hands the work on when a seat runs low.

Start the 7-day trial How it works →

Local-first · Windows · Linux · macOS beta · no card for the trial

$ hivelane-dispatch run auto "add tests for the refund flow" --capability coding --worktree --background
AUTO ROUTE: Selected codex because it is installed and matched: coding; routing priority 80; 38% used vs claude 61%. Local effort medium.
Started background job 20261014101702-b7c2e1 (agent: codex).
worktree: C:\dev\.hivelane-wt\20261014101702-b7c2e1

Real Hivelane output. Folders, ids and numbers are an example.

How it works

One agent in charge. The rest on call.

You keep talking to the CLI you like. Through Hivelane it can hand pieces of the job to the other agents on your machine, wait for the result, and check it. You approve what lands.

RTE01 · ORCHESTRATE

Orchestrate

Your main agent delegates, and Hivelane routes each task to the installed agent whose strengths match it.

Routing by capability: coding, review, research, audit
Effort set low, medium or high from the task
Each worker in its own git worktree, with file locks
Workers can't delegate again, so nothing runs away

HND02 · NEVER STALL

Never stall

When a seat nears its limit, the work moves on. In a live session you get a warning and pick who takes over. Background jobs move to the next agent on their own.

Usage read the way each CLI reads it
The next agent starts from the goal, the diff and the last checkpoint
hivelane resume from any terminal
Says "usage unknown" instead of inventing a number

MEM03 · REMEMBER

Remember

One memory shared by every agent and every session, local-first: it lives in a database on your machine. The next agent knows why, not only what changed.

Checkpoints and decisions saved as agents work
Search past decisions by meaning, with a local model such as Ollama
Similar facts merged only after you see a preview, with undo
Optional sync across machines via your own server

Remote

Laptop and server, one fleet.

Run agents on more than one machine? Connect them through your own server over SSH. Nothing goes through Yuvaan Labs.

Send work across machines. hivelane submit --repo ... --agent codex --prompt "..." puts a job on your server's queue. hivelane worker on your laptop picks it up, runs it with that agent and reports back. hivelane status shows where each job is. Workers commit locally if you ask, and never push.
One memory on every machine. Facts your agents save go to your server, and each machine pulls the combined summary, so the agent on your laptop knows what the one on your server decided.
Offline is fine. Facts wait in a local queue and go up when the connection is back.
Your server, your data. A small script on the server decides where facts live: Postgres, SQLite or plain files.

Also in the box

The parts you notice on the second day.

Small things that keep a fleet of agents from turning into a mess.

Auto handoff for background jobs --on-limit handoff

A background job that hits its seat limit moves itself to the next agent, in the same worktree, with its diff and checkpoint. You don't have to be there.

Review gate and pull requests

Finished worker jobs can be checked and opened as a PR. Hivelane never merges on its own, and won't publish when checks fail or the diff looks like it holds a secret.

Decision holds

When a task needs your call, the agent records a hold with the options and waits for you, instead of guessing. Holds survive restarts.

Supervision inbox

Background jobs report back when they finish or fail, even across a restart, so nothing ends silently.

Provider cooldowns limits

When a provider says the quota is gone, Hivelane notes the cooldown and stops sending that account work until it's back. hivelane-dispatch limits shows them.

Fleet dashboard dashboard

hivelane dashboard opens a read-only page on your machine: active jobs, worktrees, checks, PRs and anything waiting on you.

Agents that talk

An event bus lets agents publish and subscribe to each other's updates, instead of you copying messages between terminals.

Focus overlap check

Each agent declares what it's working on. Hivelane flags it when two local agents head for the same files.

Setup in one command

hivelane setup finds the coding CLIs on your machine and connects them. hivelane doctor tells you what's working.

Pricing

Try it for a week. Pay once.

The trial is the full product. If you keep it, it's one payment, not a subscription.

Trial

$0 7 days

No card. One trial per email address.

Everything in Hivelane
Key by email, works on 2 machines
When it ends, Codex and Claude Code keep working as before

Founders Edition

$29 one-time

For the first 100 buyers, then $49. No subscription.

Routing and dispatch across your agents
Handoff when a seat runs low
Shared memory, synced across your machines
Send jobs from your server to your laptop agents
Worktrees, file locks, review gate and PRs
One key, 2 machines
Works 7 days offline

Get Founders Edition for $29

Checkout by Dodo Payments. Your licence key arrives by email. 14-day refund.

Install

One line to install.

64-bit Windows or Linux (x64, glibc 2.35+, e.g. Ubuntu 22.04 or newer). Nothing else to install. Use the key from your trial or purchase email.

Windows (PowerShell)

>irm https://yuvaanlabs.com/hivelane/install.ps1 | iex

Linux

$curl -fsSL https://yuvaanlabs.com/hivelane/install.sh | sh

Then, in a new terminal

$hivelane activate <your key>
$hivelane doctor

The installer checks the download, connects Hivelane to the agent CLIs it finds and adds it to your PATH. Restart your agent sessions so they load Hivelane. hivelane doctor checks that everything is connected. Run the same line again to update; your data and licence are kept.

macOS

macOS is in private beta. Mail [email protected] and I'll set you up.

One extra step for Codex

Codex only runs hooks you have trusted. Start codex, run /hooks and trust the Hivelane hooks. Without this, Codex sessions don't get the usage warning.

Moving to another computer

Run hivelane deactivate on the old one to free its slot, then hivelane activate on the new one.

Help

Write to [email protected]. I read every mail.

FAQ

Questions

Does Hivelane send my code or prompts anywhere?

No. Hivelane is local-first. Routing, memory and checkpoints stay on your machine; if you turn on server sync, facts go to your own server over SSH. Usage is read from the sign-in your agent CLIs already keep, the same way the CLI reads it. The only thing Hivelane itself sends is the licence check to Dodo Payments, at most once a day: your key and your computer's name. Handoff data has access tokens and credentials stripped out.

What happens when the trial ends?

The Hivelane tools, dispatch and hivelane resume stop with a message, and the session hooks go quiet. Codex and Claude Code keep running exactly as they did without Hivelane. You get a reminder mail a day before.

Does it pick the next agent for me?

In a live Claude Code or Codex session, no: it shows the agents that can take over and how much each has left, and you choose. Background jobs started with --on-limit handoff move to the next agent on their own. The seat that ran low is never picked.

Do I need a local model?

Only for two memory features: searching past decisions by meaning and merging similar facts. Those use a model you run yourself, such as Ollama, so nothing leaves your machine. Everything else works without one.

Is it a subscription?

No. Founders Edition is one payment: $29 for the first 100 buyers, then $49. One key works on 2 machines.

What if I'm offline?

Hivelane keeps working for 7 days without a connection. The licence is checked at most once a day.

Does it work on Mac and Linux?

Windows and Linux, yes: one-line installers for both, tested on each release. macOS is in private beta while I test it on more machines. Mail [email protected] to join.

Will it merge code on its own?

No. If you turn on pull requests for finished tasks, Hivelane opens the PR and stops there. It won't publish when checks fail or when the diff looks like it contains a secret.