@hydra-acp/cli 0.1.200 → 0.1.202
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 +10 -0
- package/dist/cli.js +439 -436
- package/dist/daemon.js +95 -95
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -710,6 +710,16 @@ hydra-acp extension start hydra-acp-archiver
|
|
|
710
710
|
|
|
711
711
|
See the [package README](https://github.com/smagnuso/hydra-acp-archiver#readme) for backend setup (Drive OAuth, filesystem path).
|
|
712
712
|
|
|
713
|
+
**[`@hydra-acp/ahp`](https://github.com/smagnuso/hydra-ahp) — VS Code agent host.** Serves hydra sessions over the [Agent Host Protocol](https://github.com/microsoft/agent-host-protocol) so VS Code's agent UI can list, watch, and drive them. VS Code connects to it like any remote agent host, while every session stays live and shared with the TUI, browser, and Slack. Start a turn in the TUI and watch it stream in VS Code, or start a session in VS Code and pick it up later from the terminal. It listens on `127.0.0.1:55590` and mints its own token for VS Code, so hydra's tokens never leave the daemon.
|
|
714
|
+
|
|
715
|
+
```sh
|
|
716
|
+
npm install -g @hydra-acp/ahp
|
|
717
|
+
hydra-acp extensions add hydra-ahp
|
|
718
|
+
hydra-acp extensions start hydra-ahp
|
|
719
|
+
```
|
|
720
|
+
|
|
721
|
+
See the [package README](https://github.com/smagnuso/hydra-ahp#readme) for connecting VS Code and minting a token (`/hydra ahp token mint`).
|
|
722
|
+
|
|
713
723
|
**[`@hydra-acp/planner`](https://github.com/smagnuso/hydra-acp-planner) — multi-agent project orchestrator.** Invoked via `/hydra planner create <description>` from any session: asks the host agent to decompose the project into a task DAG, then spawns N worker sessions and drives them in parallel by prompt management, with progress streaming back into your original chat. Boards persist under `~/.hydra-acp/planner/projects/<id>/` so plans survive daemon restarts. Strictly speaking it's a [transformer](#transformers), not an extension — it sits in the daemon's message pipeline rather than attaching as a client — but it installs and configures the same way.
|
|
714
724
|
|
|
715
725
|
```sh
|