Watch
0
0
Fork
You've already forked hyperhive
0
hyperhive/swarm-claude-login/README.md
iris aa1ae2729f docs: the claude login page keeps the operator steps and moves the minter detail out
The queue subjects, scratch directory and stdio steps of a login, the harness's
newer-version rule, the minter's grants, the caveat and the metrics move to
4-implementation/swarm/claude-login.md. The handbook page keeps how to log an agent
in, the stored login and who may do it. Design pointers in the nix module, the
crate README and AGENTS.md name the new page.
2026-11-11 09:05:59 +01:00

20 lines
997 B
Markdown

# 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/4-implementation/swarm/claude-login.md`](../docs/4-implementation/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.