vinzenz/hyperhive
vinzenz/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Activity

document reading and editing an agent's agents.md through the swarm

Browse source 
docs/swarm/README.md gets the routes, the revision, the apply semantics
and the stopped-agent behaviour; the persistence doc points there from
the AGENTS.md entry. The swarm-controller, swarm-controller-api and
swarmctl READMEs and the repo map in AGENTS.md list the new bodies and
routes. docs/tools/swarmctl-cli.md is regenerated for
`swarmctl agent agents-md`, whose help text loses two passive phrasings
vale flags.
This commit is contained in:
atlas 2026-10-18 03:37:27 +02:00 • committed by mara
commit 9add99838c
8 changed files with 124 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

5
swarmctl/README.md
View file

@ -7,8 +7,9 @@ that talk to the controller, from anywhere as your own SSO account (see
Distinct from `hivectl`, which drives one hive's `hive-c0re` over its
admin socket. This crate doesn't link `swarm-controller`, for the same
reason `hivectl` doesn't link `hive-c0re`; the forge and schedule bodies
and the agent responses both sides speak come from `swarm-controller-api`,
reason `hivectl` doesn't link `hive-c0re`; the forge, schedule and
`AGENTS.md` bodies and the agent responses both sides speak come from
`swarm-controller-api`,
as `hivectl`'s come from `hive-host-sock`.
## Why root, and why no socket