vinzenz/hyperhive
vinzenz/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2

docs: clear write-good.Passive hits in docs/tools/hivectl.md

Browse source 
5 genuine passive-voice rewrites (actor named — create-user, hivectl,
the operator, claude, you the CLI user); 2 false positives left
untouched — predicate-adjective necessity descriptions ('is needed',
'is required'), same category already established across this sweep.
This commit is contained in:
iris 2026-09-20 13:24:11 +02:00 • committed by mara
commit ffc062707b
1 changed files with 8 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

16
docs/tools/hivectl.md
View file

@ -43,7 +43,7 @@ hivectl forge reconcile-config iris --verbose # include the full diff, not
`create-user` persists the token to `<state>/forge-token`. Re-running refreshes the `create-user` persists the token to `<state>/forge-token`. Re-running refreshes the
token (idempotent — scope always matches current `TOKEN_SCOPES`). token (idempotent — scope always matches current `TOKEN_SCOPES`).
- For **non-agents** (humans): creates the account and prints the token to - For **non-agents** (humans): creates the account and prints the token to
stdout; no state dir is created. Re-running after account already exists stdout, creating no state dir. Re-running after account already exists
re-mints the token and prints it again — safe for password resets. re-mints the token and prints it again — safe for password resets.
- Without `--password` / `--password-stdin` `create-user` uses a random - Without `--password` / `--password-stdin` `create-user` uses a random
throwaway password (fine for agents — they auth by token). throwaway password (fine for agents — they auth by token).
@ -133,8 +133,8 @@ username updates the password hash in place.
Container lifecycle shortcuts that go through the host admin socket. Container lifecycle shortcuts that go through the host admin socket.
Requires the `hive-c0re` daemon to be running. Everything scoped to a Requires the `hive-c0re` daemon to be running. Everything scoped to a
single agent lives under `hivectl agent <name> <verb>` — the name is single agent lives under `hivectl agent <name> <verb>` — `hivectl` hoists
hoisted onto the parent command, so none of the verbs below repeat it. the name onto the parent command, so none of the verbs below repeat it.
```bash ```bash
hivectl list-agents # roster: every agent's status + technical state hivectl list-agents # roster: every agent's status + technical state
@ -221,8 +221,8 @@ granting that group the one action `machinectl shell` needs); `choom`
checks this itself and refuses up front with a message naming the checks this itself and refuses up front with a message naming the
requirement rather than letting systemd reject the exec later with an requirement rather than letting systemd reject the exec later with an
opaque polkit prompt. Same caveat as the socket grant: a shell opened opaque polkit prompt. Same caveat as the socket grant: a shell opened
before you were added to `hive-admin` won't see it until you log back in before the operator added you to `hive-admin` won't see it until you log
— secondary group membership applies at login. back in — secondary group membership applies at login.
It also needs the daemon socket, unlike the other exec-into-a-container It also needs the daemon socket, unlike the other exec-into-a-container
paths: the "is this actually an agent?" pre-flight reads the agents root, paths: the "is this actually an agent?" pre-flight reads the agents root,
@ -241,9 +241,9 @@ through as `claude --resume <value>` to rejoin a prior session by its
session id — the flag name deliberately matches the claude flag it maps session id — the flag name deliberately matches the claude flag it maps
to. (choom never uses claude's `--continue`: that's a bare flag that to. (choom never uses claude's `--continue`: that's a bare flag that
takes no argument and resumes the cwd's _latest_ session, that is, the takes no argument and resumes the cwd's _latest_ session, that is, the
harness's; a value after it would be consumed as the first prompt, harness's; claude would consume a value after it as the first prompt,
silently poking the live harness session.) A value is required when the silently poking the live harness session.) A value is required when you
flag is given. Either way choom never collides with the harness's live pass the flag. Either way choom never collides with the harness's live
session in the same project dir: the harness pins its own id via session in the same project dir: the harness pins its own id via
`--resume`, so a blank choom session is invisible to it. The container `--resume`, so a blank choom session is invisible to it. The container
must be running. must be running.