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

rename choom flag --continue to --resume to match the claude flag it maps to (mara review)

Browse source
This commit is contained in:
damocles 2026-07-02 19:48:54 +02:00 • committed by mara
commit 2f43077e31
3 changed files with 36 additions and 35 deletions
Download patch file Download diff file Expand all files Collapse all files

25
docs/tools/hivectl.md
View file

@ -127,20 +127,21 @@ running claude from the agent's state dir. Requires root (same as all
`machinectl shell` operations).
```bash
hivectl choom iris # fresh blank Claude session in iris's container
hivectl choom iris --continue <session-id> # rejoin a prior session by id
hivectl choom iris # fresh blank Claude session in iris's container
hivectl choom iris --resume <session-id> # rejoin a prior session by id
```
Bare `choom` starts a fresh blank session. `--continue <value>` maps to
`claude --resume <value>` to rejoin a prior session by its session id.
(It is deliberately NOT passed as `claude --continue <value>` — claude's
own `--continue` is a bare flag that takes no argument and resumes the
cwd's *latest* session, i.e. the harness's; a value after it would be
consumed as the first prompt, silently poking the live harness session.)
A value is required when the flag is given. Either way choom never
collides with the harness's live 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 must be running.
Bare `choom` starts a fresh blank session. `--resume <value>` passes
through as `claude --resume <value>` to rejoin a prior session by its
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
takes no argument and resumes the cwd's *latest* session, i.e. the
harness's; a value after it would be consumed as the first prompt,
silently poking the live harness session.) A value is required when the
flag is given. Either way choom never collides with the harness's live
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
must be running.
choom reproduces the harness's own claude invocation so the operator
lands in a faithful copy of the agent's environment: