Add `dev agent {list,run,show}` over the canonical `/v1/agents` registry
(cloud/clients/agents), reusing the signed-in hanzo.id session for auth.
- New crate `agents-client` mirrors `cloud-tasks-client`: wire types
(Agent/AgentDetail/Run matching the server contract), an `AgentsBackend`
trait, and a reqwest `HttpClient` that targets `{base}/v1/agents…`,
injects the bearer JWT via `codex_api::SharedAuthProvider`, and quotes
server errors honestly. A recorded error run (HTTP 502 with a Run body)
is surfaced as the Run, not swallowed as a bare status.
- New `cli/src/agent_cmd.rs` module wires the subcommand like the existing
`cloud` command: resolves base URL (default https://api.hanzo.ai,
override CODEX_AGENTS_BASE_URL) + AuthManager from the loaded Config,
fails secure when not signed in. `list`/`run`/`show`, each with `--json`;
`run` reads the prompt from an arg or stdin.
- Cloud-agent invocation is additive and orthogonal to the local
config-defined subprocess agents; no shared state.
Tests: 8 wiremock unit tests (list/get/run happy + recorded-error 502 +
503 server error + bearer header + path encoding). `cargo build`, `cargo
clippy -D warnings`, and `cargo test` are clean for the touched crates.
Bumps @hanzo/dev 0.6.91 -> 0.6.92 (patch) so a release can publish.
Create parallel dev-cli/ package structure for @hanzo/dev npm distribution:
- Add bin/dev.js entry point that resolves platform binary
- Add postinstall.js for binary download on install
- Add scripts/preinstall.js for Windows cleanup
- Add scripts/windows-cleanup.ps1 PowerShell helper
Update release workflow to:
- Create @hanzo/dev-* platform packages alongside @just-every/code-*
- Rename code-* binaries to dev-* in @hanzo/dev packages
- Update dev-cli/package.json with version and optionalDependencies
- Publish @hanzo/dev main package to npm
This fixes the broken @hanzo/dev npm package which was missing
platform binary packages (@hanzo/dev-darwin-arm64, etc.)
zeekay
GitHub Action