@hydra-acp/cli 0.1.151 → 0.1.152
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 +6 -1
- package/dist/cli.js +395 -391
- package/dist/daemon.js +103 -101
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -279,6 +279,9 @@ hydra-acp --reattach # reattach to this terminal's last s
|
|
|
279
279
|
hydra-acp --new # force a fresh session
|
|
280
280
|
hydra-acp --readonly # open a session as a transcript viewer (with --session)
|
|
281
281
|
hydra-acp --dangerously-skip-permissions # auto-approve every tool permission request
|
|
282
|
+
# (tui.skipPermissions makes this the default;
|
|
283
|
+
# --no-dangerously-skip-permissions refuses it
|
|
284
|
+
# for one run)
|
|
282
285
|
|
|
283
286
|
hydra-acp init [--rotate-token] # generate the service token
|
|
284
287
|
hydra-acp version [--json] # CLI, daemon, and extension/transformer versions
|
|
@@ -478,7 +481,7 @@ conversation log.
|
|
|
478
481
|
| `/hydra compact [status]` | Compact history now. `status` inspects state without triggering. |
|
|
479
482
|
| `/hydra uncompact` | Roll back the most recent compaction, before any new turns. |
|
|
480
483
|
| `/hydra fork [verbatim]` | Fork into a new session. Default is a synopsis brief; `verbatim` slices at the last completed turn. |
|
|
481
|
-
| `/hydra workspace <start [name] [--clean] \| sync \| merge \| stop \| detach \| clean [--deep] \| discard \| status>` | Move this session into an isolated checkout and land, park, or throw away the work. `start --clean` leaves your uncommitted changes behind instead of copying them in; `clean` wipes the workspace and stays in it. See [isolated workspaces](#isolated-workspaces). |
|
|
484
|
+
| `/hydra workspace <start [name] [--clean] \| sync \| merge \| apply \| stop \| detach \| clean [--deep] \| discard \| status>` | Move this session into an isolated checkout and land, park, or throw away the work. `start --clean` leaves your uncommitted changes behind instead of copying them in; `apply` stages the work into your tree without its history; `clean` wipes the workspace and stays in it. See [isolated workspaces](#isolated-workspaces). |
|
|
482
485
|
| `/hydra restart` | Restart the agent with a fresh `session/new`, preserving history. Useful when the available models have changed underneath you. |
|
|
483
486
|
| `/hydra kill` | Close this session. The agent dies; the record is kept and can be resumed. |
|
|
484
487
|
|
|
@@ -568,6 +571,8 @@ one is to sit on that row and walk through them. Eighteen ship built in, and
|
|
|
568
571
|
|
|
569
572
|
`tui.defaultEnterAction` (default `"amend"`) controls what the unmodified Enter key does in the prompt composer. With `"amend"` (the default), Enter amends the in-flight turn and `Shift+Enter` enqueues a new prompt; with no turn in flight either key just enqueues, since there's nothing to amend. Set to `"enqueue"` to flip the two: Enter enqueues (sends immediately when idle, queues behind an in-flight turn) and `Shift+Enter` amends.
|
|
570
573
|
|
|
574
|
+
`tui.skipPermissions` (default `false`) makes `--dangerously-skip-permissions` the standing default for the TUI: every tool permission request is auto-approved (with `allow_once`, so nothing is written to the agent's persisted permission rules) and the modal never appears. The startup banner names the config key so it isn't silent. TUI-only on purpose: `shim`, `launch`, and `cat` are spawned by editors and scripts with their own argv, and an ambient config key there would disarm paths you aren't watching. Pass `--no-dangerously-skip-permissions` to get the prompts back for a single run.
|
|
575
|
+
|
|
571
576
|
## Extensions
|
|
572
577
|
|
|
573
578
|
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.
|