Self-hosted · Source-controlled · Local-first

One agent is not enough.
A pile of terminals is not a workflow.

HiveTeam puts an Orchestrator in charge: it dispatches work while real CLI agents — Claude Code, Codex, Gemini — each do their part in browser terminals. Everything runs on your machine, and every line of code lives in the repo you cloned.

01

You give the Orchestrator a goal

02

It dispatches workers with team send

03

Workers finish and team report back

Real screenshot

No staging. Just the workbench.

The Orchestrator's terminal is dispatching on the left; four teammates work on the right — a frame from a real delivery run, not a mockup.

127.0.0.1:3000
HiveTeam workbench: the orchestrator terminal dispatches tasks while four worker cards show live status

Every teammate is a card: running, idle, stopped — the whole team at a glance.

Three ways to split the work

No heroes in the hive.

No single agent ships the whole project. Each one owns the part it is best at.

$ team send claude
"write: dark mode for settings"

$ team send codex
"review: find flaws in this diff"

codex report:
2 edge cases, needs another pass

Write + Review

Two models tearing each other's work apart beats one model grading its own homework. You only read the final diff.

$ team send gemini
"write tests, run the full suite"

gemini report: 3 reds

$ team send claude
"fix these 3 reds"

Test + Fix

The red-green loop spins inside the hive. What counts as green, and when to stop — that's your call.

$ team send researcher
"verify the 5 cited sources"

$ team send translator
"translate findings to English"

researcher report:
2 don't hold up, citations attached

Beyond Code

Researcher, translator, screenwriter, debate partner — name a role, and the Orchestrator does the scheduling.

Features

Dispatching is just the start.

What makes a team of agents actually usable is everything around the dispatch.

team spawn · experimental · on by default

Auto-staffing

Don't want to build a team by hand? Don't. The Orchestrator hires temporary coders, testers and reviewers per task, and dismisses them when the work comes back.

workflows · experimental · opt-in

Multi-stage workflows

Split a goal into fan-out, review and test stages and run them end to end. Run records, logs, schedules and the stop button all live in the Workflows panel.

memory

Team memory

Workspace constraints, conventions and earlier decisions stay in the hive, and every later dispatch brings them to the right agent — no repeating yourself.

.hive/tasks.md

The task graph is markdown

Your task graph sits in the repo: read and edit it in any editor, commit it to git. Tasks can declare dependencies ([needs: #3]), so blocked work never gets handed out early.

--resume

Resume after restart

After a restart, each agent first tries its CLI's native session resume; if that fails, a fresh process gets an auto-written handoff brief. Queued tasks survive too.

marketplace

Role template market

Coder / Reviewer / Tester templates are built in and editable; 400+ bilingual community role templates ship with the repo — search, one-click import, works offline.

Also: multi-workspace sidebar · desktop notifications & alert sounds · installable as a PWA · open a workspace in VS Code / terminal with one click · bilingual UI

This fork

A hive you own is a hive whose source you hold.

HiveTeam is a source-controlled, self-hosted fork: every line you run can be found in the commit you checked out.

one repo

Everything in one repo

The runtime, the web workbench, and the remote-access gateway in gateway/ — all in this one repository. No closed-source parts, no surprises in the install.

no update channel

No update channel

It never asks npm or the upstream release feed what's new. Upgrading is git pull — you always run the version you picked, and the diff tells you what changed.

127.0.0.1 only

Localhost by default

The server binds 127.0.0.1; nothing listens beyond your machine. Remote access is off by default — until you flip the switch, the path simply doesn't exist.

license in the open

The license, in plain sight

BSL 1.1: personal use, internal deployment and forks are all fine; names and marks are governed by TRADEMARK.md. Pointing it at sensitive repos? Read SECURITY.md first.

Roster

Already in the hive — and who can join.

Nine presets work out of the box, and that's just the start. Any agent that runs on your machine runs in HiveTeam: reuse the CLIs you've already signed into — HiveTeam itself needs no account and no API key.

Claude Code Codex CLI Gemini CLI OpenCode AAntigravity CCursor CLI GGrok Build HHermes QQwen Code $custom command

You install and sign into each CLI yourself — HiveTeam never installs agents or touches your credentials. It just turns them into a team.

Remote Access · optional · off by default

You left the house. The hive stayed awake.

Sign in from your phone's browser, pair with the desktop once, and open your running hive from anywhere — not just to watch: the terminal takes real input on your phone, and work keeps flowing.

End-to-end encrypted

Ciphertext from phone to machine; the gateway only relays. Data and execution never leave your box.

No open ports

Your machine dials out. No public IP needed, no ports exposed.

Trust rooted at the desktop

Pairing a new device requires someone physically at the computer to confirm. Any device can be revoked at any time.

Gateway source included

The remote gateway's implementation lives in the repo's gateway/ directory — audit the encryption path yourself.

Install

Four commands to a hive.

Requires Node.js ≥ 22 and pnpm. macOS / Linux are first-class; Windows is best-effort.

terminal
$ git clone https://github.com/zhouyuanxinand/hiveteam.git
$ cd hiveteam
$ pnpm install
$ pnpm dev
# open the local address it prints, usually http://127.0.0.1:3000

Updating is just as plain: git pull, then pnpm install --frozen-lockfile && pnpm build, and restart the process.