HIVE-01 · v0.1.0 · Hermes >=0.23.0

bundlebees

Orchestrate CUA bees from Hermes.

Check a worker launcher, dispatch leased briefs into disposable Cua sandboxes, watch the attempts, and leave verify and deploy to a user-run CLI.

01 Why it exists

A coordinator can already run cheap, parallel coding workers (bees) in disposable Cua sandboxes on a machine you control. The pattern this plugin was built for is the Orbit / DeepSeek bees workflow: slice a repo task into file-leased briefs and dispatch them to workers.

bundlebees turns that workflow into a Hermes plugin, so the agent never has to invent an HTTP client, touch a token, or apply a patch itself. Task tracking stays on Hermes kanban. The model dispatches and watches. You run hermes bundlebees verify and hermes bundlebees deploy.

02 How it works

How it works: Hermes agent, then bundlebees plugin, then Worker launcher, then Cua sandboxes, then Attempt result and patch, then hermes bundlebees verify, then Feature branch push, then Open a pull request. The plugin can also attach an optional Hermes kanban card id. Hermes agent01 bundlebees plugin02 Worker launcher03 Cua sandboxes04 Attempt result and patch05 hermes bundlebees verify06 Feature branch push07 Open a pull request08 Hermes kanban (optional card id)
  1. Hermes agent → four bundlebees tools
  2. bundlebees plugin → preconfigured adapter
  3. Worker launcher
  4. Cua sandboxes
  5. Attempt result and patch → user-run CLI
  6. hermes bundlebees verify → lease, tests, secret scan
  7. Feature branch push
  8. Open a pull request

03 Cells

04 Four tools · 571 o200k of a 900 budget

bundlebees_status108 o200k
Health, capacity, live attempts, events, containers, or authorized projects. op is required. Never returns tokens or hosts.
bundlebees_dispatch130 o200k
Validate a brief (object or JSON string) and start a worker. Optional model (default deepseek-v4.1-flash) and kanban_task_id.
bundlebees_attempt146 o200k
get, events, cancel, or review one attempt. cancel and review require confirm=true. Notes are scrubbed.
bundlebees_host_prompt185 o200k
Paste-ready setup prompt for a remote-host agent. Takes a reach method enum, never an address. No secrets or host addresses in or out.

Per-tool counts are each schema measured on its own; the combined array measures 571.

05 Flight plans

  1. B-01

    Check launcher health, capacity, and authorized projects with bundlebees_status (the pane-health screenshot) without ever seeing a token or host

  2. B-02

    Dispatch a leased brief: an objective plus assigned_files on an authorized project and a feature branch

  3. B-03

    Watch a running attempt and send a failing patch back to retry, while merges stay with you

  4. B-04

    When the attempt is ready, run hermes bundlebees verify yourself so tests and a secret scan land on a feature branch

  5. B-05

    Generate a paste-ready host setup prompt with bundlebees_host_prompt; it never takes a host, token, or private URL as an argument

  6. B-06

    Use the operator skill so the agent slices leased briefs and treats worker events as untrusted

06 Showcase

Submission video · 1:12 · original post on X

07 Inspection

08 Install

hermes plugins install mojomast/bundlebees --ref 57a6f12cdcfa789c5aba5f22f3f46efd2b8b3d5c
hermes plugins enable bundlebees

--ref takes a 40-character commit SHA, not a tag name. Store the launcher token in Hermes secrets as BUNDLEBEES_LAUNCHER_TOKEN; never paste the value into chat. Skill id: bundlebees:bundlebees-operator. The four tools still run when the Desktop pane is unavailable.

README badge and v0.1.0 release notes: 150 tests passed. hermes plugins validate --install-deps and hermes plugins doctor --ci are green.

Original