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

feat(#2067): choom --continue passes through to claude --continue (drop --resume translation)

Browse source
This commit is contained in:
damocles 2026-06-28 23:41:08 +02:00 • committed by mara
commit 0125fcfae8
3 changed files with 51 additions and 43 deletions
Download patch file Download diff file Expand all files Collapse all files

9
docs/tools/hivectl-cli.md
View file

@ -379,14 +379,17 @@ Generate the federation peer-config block for THIS hive — the nix a peer opera
Open an interactive Claude session inside an agent container.
Execs `machinectl shell <name>@h-<name>` running claude as the agent user from its state dir, with the same settings / MCP config / system prompt the harness uses. Without a session id you get a fresh blank session each launch; pass one to resume an earlier choom session (`--resume <id>`). Either way it never collides with the harness's live session — the harness pins its own session id via `--resume`, so a blank choom session is invisible to it. Requires root + a running container.
Execs `machinectl shell <name>@h-<name>` running claude as the agent user from its state dir, with the same settings / MCP config / system prompt the harness uses. Bare `choom <name>` launches a fresh blank session; `choom <name> --continue <id|name>` passes `--continue <value>` straight through to claude to rejoin a prior session (claude resolves whether the value is a session id or a display name). It never collides with the harness's live session — the harness pins its own session via `--resume`, so a blank choom session is invisible to it. Requires root + a running container.
**Usage:** `hivectl choom <NAME> [SESSION]`
**Usage:** `hivectl choom [OPTIONS] <NAME>`
###### **Arguments:**
* `<NAME>` — Agent name (e.g. `damocles`, `iris`)
* `<SESSION>` — Optional session id to resume (`claude --resume <id>`). Omit for a fresh blank session
###### **Options:**
* `--continue <SESSION>` — Resume a prior claude session by id or display name, passed through as `claude --continue <value>`. Omit for a fresh blank session. A value is required when the flag is given

18
docs/tools/hivectl.md
View file

@ -127,16 +127,18 @@ 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 <session-id> # resume an earlier choom session
hivectl choom iris # fresh blank Claude session in iris's container
hivectl choom iris --continue <id|name> # rejoin a prior session by id or display name
```
With no session id, claude starts a fresh blank session (mints its own
id). Pass a session id to resume it (`claude --resume <id>`); you can
rename it in-session. 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. `--continue <value>` is
passed straight through as `claude --continue <value>` to rejoin a
prior session — claude resolves whether the value is a session id or a
display name (you can `/rename` a session in-session for an easy
handle). 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: