@hydra-acp/cli 0.1.6 → 0.1.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -1
- package/dist/cli.js +2185 -634
- package/dist/index.d.ts +68 -5
- package/dist/index.js +471 -106
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -210,7 +210,7 @@ hydra-acp daemon status
|
|
|
210
210
|
|
|
211
211
|
hydra-acp sessions # list sessions
|
|
212
212
|
hydra-acp sessions kill <id> # close a live session (keeps the on-disk record so it can be resurrected)
|
|
213
|
-
hydra-acp sessions
|
|
213
|
+
hydra-acp sessions remove <id> # remove a session entirely (live or cold)
|
|
214
214
|
hydra-acp sessions export <id> [--out <file>|.]
|
|
215
215
|
# write a session bundle (meta + history) to <file>,
|
|
216
216
|
# to a default-named file when --out=., or to stdout
|
|
@@ -347,6 +347,8 @@ When you ask hydra to spawn an agent (via `launch <agent>`, `--agent`, or `HYDRA
|
|
|
347
347
|
|
|
348
348
|
`daemon.sessionRecentMinutes` (default 30) controls how far back `hydra-acp sessions` (and the `/v1/sessions` REST endpoint without `?all=true`) looks for cold (disk-only) sessions. Set to `0` to never list cold sessions.
|
|
349
349
|
|
|
350
|
+
`tui.mouse` (default `true`) controls whether the TUI captures mouse events. With capture on, the scroll wheel drives scrollback but selecting text requires `shift+drag` to bypass mouse reporting in your terminal. Set to `false` to disable capture — plain click-drag selects text, but wheel-driven scrollback stops working (use `PgUp` / `PgDn` instead).
|
|
351
|
+
|
|
350
352
|
### Extensions
|
|
351
353
|
|
|
352
354
|
Hydra can spawn user-configured extension processes when the daemon starts. Extensions are arbitrary commands — written in any language — that talk to the daemon over its existing REST or WSS endpoints. Hydra handles their lifecycle (spawn on start, kill on stop, auto-restart on crash with exponential backoff up to ~60s) and injects daemon connection info via env vars.
|