Watch
0
0
Fork
You've already forked hyperhive
0
hyperhive/swarm-claude-login/README.md
iris 6739bb903d docs: sort the top-level directories into five sections by what the reader wants
Every docs directory moves under 1-getting-started, 2-handbook,
4-implementation or 5-project; the options reference (section 3) comes from
the website and has no directory here. trust-boundary stays whole under the
handbook for now. web-ui, swarm and tools split between handbook and
implementation, and the command-line references move to
2-handbook/reference. Links, path references in code and nix, and the docs
index follow the moves; no page content changes.
2026-11-06 18:46:57 +01:00

985 B

swarm-claude-login

The claude login minter, in the swarm-claude-login container on the host that sets deploy.claude-login.enable. The design is docs/2-handbook/swarm/claude-login.md.

swarm-controller relays an operator's login of one agent as two requests on $SWARM.claude-login.request: a start, answered with the URL claude auth login printed, and the code the operator pasted, answered once the agent's .credentials.json is stored at swarm/agents/<agent>/claude-credentials. Each login runs with HOME and CLAUDE_CONFIG_DIR in its own scratch directory, removed when the login ends however it ends.

Credentials

The container holds one credential: its own store certificate, which nspawn hands in at start without a copy on disk. With it the service reads its queue client secret, and writes the claude-credentials leaf of any agent, a new version over the last. Its store role can do exactly those two things.