| Filename | Latest commit message | Latest commit date |
|---|---|---|
e3864fe787
`matrix.md` documents the exact text of every inbound matrix signal — three wake-body shapes and the invite loose-end — and none of them mention that the daemon prefixes `[acct:<name>] ` when it serves more than one account. `wake::tag_account` is live on both documented paths (`timeline.rs:75` for unread wakes, `:139` for invite todos), so an agent with an extra account receives `[acct:ccc] [matrix] @a:s in #x: hi` where the page promises a body starting `[matrix]`. The example is not hypothetical: the matrix module uses `matrix-token-ccc` on dmatrix as its worked example of an extra account. It stayed invisible because the `None` arm returns the body unchanged, so every single-account agent sees the documented format exactly. The page is right for almost every reader and wrong for precisely the readers its "Multiple accounts" section is written for. Two placements rather than one. The prefix itself goes next to the wake formats it corrects, with the worked example and the reason a leading `[matrix]` match works until a second account exists. A forward pointer goes in "Multiple accounts", because that is the section someone configuring extra accounts actually lands on, and it previously covered only the outbound `account` parameter — the half you pass, not the half you parse. Closes #4243. |
||
| .. | ||
| bash.md | ||
| forge-cli.md | ||
| forge.md | ||
| hivectl-cli.md | ||
| hivectl.md | ||
| lifecycle.md | ||
| matrix.md | ||
| README.md | ||
| scheduling.md | ||
| subagent.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. No curated guide yet (one verb,user add, doesn't need one); 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. - lifecycle — kill/start/restart/update for the agents in a caller's own subtree, plus the approval-gated config-change tools.
- 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) and the diagnostics tools (
get_logs,get_host_journal).