Skip to content

v2.9.0 - ACP transport

Choose a tag to compare

@nordsym nordsym released this 24 Aug 18:41
· 86 commits to main since this release

New: apiclaw acp

apiclaw acp runs APIClaw as an ACP (Agent Client Protocol) agent over stdio, for Buzz (block.xyz) and other ACP-speaking clients to spawn directly.

  • Built on the official @zed-industries/agent-client-protocol SDK, protocol version 1 (the integer PROTOCOL_VERSION, not a semver string).
  • Agent-side lifecycle: initialize (advertises the apiclaw-session auth method), authenticate (honest - if no local session it returns a JSON-RPC auth_required error pointing at apiclaw auth login, since ACP cannot drive an interactive browser login), newSession, prompt, cancel.
  • Deterministic command grammar, no LLM involved:
    • help
    • discover <query>
    • details <provider>[/<action>]
    • call <provider>/<action> [json]
    • balance
    • status
  • Reuses the existing gateway business logic from src/cli/commands/direct.ts (sendGatewayRequest, buildCallGatewayRequest) instead of duplicating it. Unauthenticated calls never touch the network - they return apiclaw auth login guidance immediately.

Docs

Added an ACP section to landing/public/agents.md, landing/public/llms-full.txt, and one line in the CLI section of the docs page.

Version

Bumped 2.8.9 -> 2.9.0 across package.json, package-lock.json, the MCPB manifest, health endpoints, layout JSON-LD, and the CLI's own VERSION constant.