| Filename | Latest commit message | Latest commit date |
|---|---|---|
d547ae58e6
mara's ruling on the review: documentation describes functionality as is. The dashboard doc carried a "Topology tree" section marked dormant, still spelling out the indent lanes, joints and continuation bars the renderer paints — for a renderer that, with no parent field to walk, puts every container at depth 0 and emits no prefix column at all. A section labelled dormant is still a section describing a feature the code does not have. Each one now states what the page renders today: SW4RM's C0NTAINERS is a flat alphabetical list, one row per container, no indent and no glyph; the tree section says nothing nests and names the code that decides so; the selection bar lists the bulk actions it has, without a note about the M0V3 picker it doesn't (agent-hierarchy.md's removal table is where that record belongs). Two more the -U15 context sweep turned up outside that section, neither naming a removed identifier so neither reachable by grep: approvals.md told an agent to clone "the child's" config repo, and hivectl.md sold `agent restart` as a way round "the agent hierarchy". |
||
| .. | ||
| bash.md | ||
| forge-cli.md | ||
| forge.md | ||
| hivectl-cli.md | ||
| hivectl.md | ||
| matrix.md | ||
| README.md | ||
| scheduling.md | ||
| subagent.md | ||
| swarm-logs-cli.md | ||
| swarmctl-cli.md | ||
Tools
hivectl is your tool — the operator's own host CLI. Everything
else here documents the tool surface your agents get inside their
containers (the MCP tools an agent's own claude session can call).
You never call these directly, but they're the reference for what an
agent can actually do — useful when you're trying to understand or
debug agent behavior.
For the operator
- hivectl — the curated guide: provisioning forge and matrix accounts, gateway htpasswd management, container lifecycle shortcuts, interactive agent shell access.
- hivectl-cli — the exhaustive, autogenerated flag-by-flag reference, kept in lockstep with the binary by CI.
For the swarm operator
- swarmctl-cli — the exhaustive, autogenerated
flag-by-flag reference for
swarmctl, kept in lockstep with the binary by CI the same wayhivectl-cli.mdis.swarmctlitself runs as root on the swarm-controller host, not throughhivectl— seeswarmctl/README.mdfor why. Two verb families today:user(authelia's subject store, edited in place) andagent create(queues the swarm-controller's creation job graph). No curated guide yet; add one here if/when that grows.
What your agents can do
- bash — background shell execution (
mcp__bash__*), available on every agent unconditionally. - subagent — spawn nested headless claude sessions
(
mcp__subagent__{start,continue,status,interrupt}), shipped default-on for every agent today alongsidebash(expected to become a real opt-in capability later). - forge — the
hive-forgeForgejo CLI every agent has for issues, PRs, and comments. Not an MCP tool — a binary agents shell out to instead of ad-hoc curl. - forge-cli — the exhaustive, autogenerated
flag-by-flag reference for
hive-forge, kept in lockstep with the binary by CI the same wayhivectl-cli.mdis. - matrix — the matrix MCP tool surface
(
mcp__matrix__*) for agents with a matrix account, multiple accounts per agent, and declaring extra MCP servers generally. - scheduling — scheduled prompts (operator approval required).