Agent workflows
Installed skills
Section titled “Installed skills”hive init writes four skills to .claude/skills/ plus an agentic section in
CLAUDE.md; hive add skill refreshes them:
| Skill | Activates on |
|---|---|
hive-work |
An issue key (MYP-42) or status/comment/acceptance request — the execution contract |
hive-workflow |
Multi-agent orchestration requests |
hivemind |
Running inside hivemind ($HIVEMIND_TILE set) or coordination requests |
hive-browser |
Web browsing from a hivemind tile |
Everything runs through the hive CLI from Bash; any runtime that executes shell
commands can participate. State flow: CLI → markdown write → filesystem watcher → board
tile.
Execution contract (per issue)
Section titled “Execution contract (per issue)”hive show MYP-42 --json— read title, description,acceptanceCriteria(0-based order matters below).- Claim:
hive ctl set-state MYP-42 in_progress, thenhive update MYP-42 --assignee <agent> --assignee-type agent. - Branch if the repo uses feature branches (
git switch -c MYP-42). - Post the plan as one comment:
hive ctl add-comment MYP-42 "plan: …". - Work; after each criterion:
hive ctl mark-acceptance MYP-42 <index>. - Verify (tests/typecheck/build), commit with the id. Do not push unless asked.
- End with a disposition — every session:
in_review,done(explicit authority only),in_progress --note "<stopped at>", orcancelled --note "<why>".
A session without a final set-state leaves the issue stale. Review comments from the
diff tile arrive as prompts (Review comment on src/x.ts:42 …); record, fix, re-verify,
and return to in_review.
Control plane
Section titled “Control plane”Inside a spawned tile ($HIVEMIND_TILE set), an agent can drive the app through the CLI:
# Start a worker with its default modelhive ctl spawn --agent pi --prompt "Review the current diff and report concrete bugs."
# Fanout; worker tiles close after replies are gatheredhive ctl workflow --shape fanout --items "auth || billing || search" \ --prompt "Review the {item} module and list concrete bugs." --close --jsonPractical rules:
- Keep
read --timeoutbelow your tool’s Bash limit (default wait is 100 s, built from ≤ 10 s polls, so retrying is safe). A timeout exits 4 withfinalStatus:"timeout"; callreadagain to collect the turn. workflow --agent codexexits 7 before spawning — codex has no turn signal; use claude, droid, pi, or kiro for workers.hive ctl stream <tile> --lines 40 --snapshotshows a tile’s screen (ANSI-stripped) for runtimes that cannot be read deterministically.hive ctl open-review --file plan.mdopens a review tile and waits for a human decision (default ceiling 24 h).
Supervision
Section titled “Supervision”spawn --supervise all (or a tool list) routes a worker’s permission prompts to you:
[hive] APPROVAL — worker … wants to run Bash: … reqIdAnswer with hive ctl approve <reqId> allow|deny|always|never. always/never are
remembered per worker+tool; on timeout or absent supervisor the prompt falls back to the
human. Only claude and kiro broker; pi is refused (no permission system).
Browser
Section titled “Browser”Opt in via Settings, then a spawned agent can drive the visible Browser tile over CDP
via the hive-browser skill (agent-browser CLI): navigate, click, fill, screenshot
the page you are watching. No hidden browser is started; the agent checks
$HIVEMIND_BROWSER_TARGETS and reports if the bridge is off or no tile is open.