| Filename | Latest commit message | Latest commit date |
|---|---|---|
15890f9d5b
16 of the 23 error-level hits from a full-repo vale run were real: 'is/are/does/do NOT' and bold 'not' expanded per Microsoft.Contractions, one hyphen-as-negative-number fixed to an en dash per Microsoft.Negative (docs/web-ui/dashboard.md's -45 deg column-header tilt). Where the caps/bold was there for emphasis (contrasting X does this, Y does not), kept the emphasis by bolding the contraction rather than dropping it silently -- 'is not' -> 'isn't', 'does NOT' -> '**doesn't**', etc. docs/tools/swarmctl-cli.md's one genuine hit is generated -- fixed the source doc comment in swarmctl/src/main.rs and regenerated via 'cargo run --bin swarmctl -- markdown-docs', diffed against the old copy first to confirm only the intended line changed. Left 7 hits unfixed, false positives from the rule matching a substring rather than the actual pattern it names: - 4x 'that's instead of that is': every one is the explanatory 'that is' idiom (~= i.e.), not a contractible subject+verb -- 'that's' would misparse as a demonstrative-pronoun contraction and change the sentence's meaning. docs/integrations/forge.md:282, docs/tools/forge.md:260, docs/tools/hivectl.md:243, docs/web-ui/dashboard.md:457 (and the swarmctl-cli.md generated twin of the same category, source left alone for the same reason). - docs/agent-lifecycle/persistence.md:482 -- 'is not' matched inside 'is nothing' (the same has-not/has-nothing substring trap noted before in this doc's own git history). - docs/swarm/ca.md:182 -- 'it is' matched inside the already-correct 'it isn't'. Per #4128. Remaining errors on main after this: Microsoft.Avoid's 26 hits, already tracked + awaiting a house-style ruling on #4041. |
||
| .. | ||
| bash.md | ||
| forge-cli.md | ||
| forge.md | ||
| hivectl-cli.md | ||
| hivectl.md | ||
| lifecycle.md | ||
| matrix.md | ||
| README.md | ||
| scheduling.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. - 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 an agent's own direct children, 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).