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

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

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: