Watch

History

Repository files (latest commit first)
Filename	Latest commit message	Latest commit date
atlas 1d56a74aad hive-forge: fetch issue comments in one request; the endpoint has no paging The forge's issue-comments endpoint takes no page or limit and always returns the whole thread. #5055 wrapped view's fetch in all_pages, which never saw a short page on a thread of 50+ comments and fetched the same list 50 times: `issue view 3782` printed 3000 comments instead of 60. `comments --limit K` sent K as a page size the forge ignored, so it returned the whole thread. view and pr status's last_comment now send one request. comments fetches the thread once and cuts the --limit / --tail window client-side; the X-Total-Count probe and the computed-page tail walk are gone, and the count of comments outside the window is the length of the list. --since is unchanged. tests/comments_no_paging.rs runs the binary against a loopback mock forge whose comments route ignores page and limit, as Forgejo's does.		2026-10-09 21:19:47 +02:00
..
bash.md	docs: drop statements about absent things, state current behaviour	2026-10-02 11:43:10 +02:00
forge-cli.md	hive-forge: drop subscription --ignore entirely — Forgejo only has watch/unwatch	2026-10-09 13:26:43 +02:00
forge.md	hive-forge: fetch issue comments in one request; the endpoint has no paging	2026-10-09 21:19:47 +02:00
hivectl-cli.md	swarm-ci-runner: run the forge CI runner as a swarm service	2026-10-05 13:55:37 +02:00
hivectl.md	docs: config changes are operator merges on the forge	2026-10-02 23:13:04 +02:00
matrix.md	hive-matrix-mcp: fix list_rooms/list_invites docs to say room_id, not id	2026-10-04 20:40:15 +02:00
README.md	docs: scheduled prompts are swarm-level; the hive page is a read-only list	2026-10-04 21:23:31 +02:00
subagent.md	hive-subagent-mcp: a refused continue leaves the session's records alone	2026-10-07 13:18:07 +02:00
swarm-logs-cli.md	docs: gate write-good.Passive on CI	2026-09-20 16:24:11 +02:00
swarmctl-cli.md	swarm: named scheduled prompts for one or more agents, fired in each agent	2026-10-04 17:24:57 +02:00

README.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 way hivectl-cli.md is. swarmctl itself runs as root on the swarm-controller host, not through hivectl — see swarmctl/README.md for why. Two verb families today: user (authelia's subject store, edited in place) and agent 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 alongside bash (expected to become a real opt-in capability later).
forge — the hive-forge Forgejo 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 way hivectl-cli.md is.
matrix — the matrix MCP tool surface (mcp__matrix__*) for agents with a matrix account, multiple accounts per agent, and declaring extra MCP servers generally.