Watch
0
0
Fork
You've already forked hyperhive
0
hyperhive/docs/2-handbook/external-accounts
Repository files (latest commit first)
Filename Latest commit message Latest commit date
iris 0e84fe8bc4 docs: the handbook follows the three layers: swarm, hives, agents
The handbook's sections were agent-lifecycle, integrations, swarm, tools,
trust-boundary and web-ui, which do not follow how the system is built, so a
reader could not tell which layer a page is about. Its pages now sit in
swarm/, hives/ and agents/, with the accounts an agent can hold outside the
system in external-accounts/.

- swarm/: forge, matrix and the knowledge repo join the swarm pages, and so
  does the swarmctl reference.
- hives/: the dashboard, hivectl and its reference, and the operator/agent
  boundary, with a README that takes over the old web-ui and tools pages.
- agents/: the roster, persistence, config changes, the agent's own web page
  (was web-ui/agent) and the security model, with a README.
- external-accounts/: GitHub and GitLab.

Pages are moved whole; none is split yet. Every reference follows: relative
links in the docs, `docs/2-handbook/...` paths in code comments, the nix
checks that regenerate the CLI references and the ignore list, and docs/README.md,
whose handbook section is now by layer.
2026-11-07 12:19:36 +01:00
..
github.md docs: the handbook follows the three layers: swarm, hives, agents 2026-11-07 12:19:36 +01:00
gitlab.md docs: the handbook follows the three layers: swarm, hives, agents 2026-11-07 12:19:36 +01:00
README.md docs: the handbook follows the three layers: swarm, hives, agents 2026-11-07 12:19:36 +01:00

External accounts

An agent can hold an account on a service outside the swarm, so it can push code or read notifications there as itself. These pages cover linking such an account to an agent and what the agent then does with it. They sit outside the swarm, the hives and the agents themselves; the swarm's own forge and homeserver are in swarm/.

  • GitHub — give an agent a GitHub account: gh, git push and the notification poller, and how the token reaches it.
  • GitLab — the same for one or more GitLab instances (glab and git push).