Busybees

🐝 busybees

**busybees** is a lightweight software factory: a Go CLI (`bees`) that runs a staff of headless [Claude Code](https://claude.com/claude-code) sessions — product manager, project manager, developers, reviewers and QA — against a single GitHub repository.

Humans steer it through GitHub. Create and label issues, comment, merge pull requests; the bees do the rest. Every role runs in its own temporary git worktree, talks to the other roles through a local mailbox, and is configured by one file: `bees.toml`.

Contributing to busybees itself? See [CONTRIBUTING.md](CONTRIBUTING.md).

Install

macOS and Linux, on amd64 (x86-64) and arm64:

curl -fsSL https://raw.githubusercontent.com/kpenfound/busybees/main/install.sh | sh

The script downloads the latest [release](https://github.com/kpenfound/busybees/releases), checks it against the SHA-256 sums published with it, and installs the `bees` binary in `/usr/local/bin` — using `sudo` only if that directory is not writable. Re-running it upgrades an existing install in place. `BEES_VERSION` picks a release and `BEES_INSTALL_DIR` where it goes; both go on `sh`, not on `curl`:

curl -fsSL https://raw.githubusercontent.com/kpenfound/busybees/main/install.sh |
    BEES_VERSION=v0.2.0 BEES_INSTALL_DIR="$HOME/.local/bin" sh

Anywhere the script does not cover — Windows, another architecture, or a build of unreleased `main` — build from source with Go 1.25+ instead:

go install github.com/kpenfound/busybees/cmd/bees@latest

[Releasing](docs/releasing.md) describes what a release contains and how to install one by hand.

Quick start

You need [`gh`](https://cli.github.com/) (authenticated), `git`, and Claude Code (`claude`), logged in. Inside a clone of the repository you want built:

bees init --template issue-driven   # writes bees.toml, creates .bees/ and the GitHub labels
bees run                            # draws a live view; --no-tui logs instead

Then open an issue de