acp-http-client is a TypeScript-first client library designed for interacting with Agent Computer Protocol (ACP) JSON-RPC services over streamable HTTP. It facilitates communication with a 'sandbox agent,' enabling operations such as desktop computer-use APIs, agent computer providers, and lifecycle management features like auto-pause support. The library is part of the larger Rivet Sandbox Agent project, which focuses on advanced agent capabilities for AI agents. Currently, the stable version is 0.4.2, with active development progressing towards 0.5.0, as indicated by recent release candidates (e.g., 0.5.0-rc.3). Development appears continuous, with frequent releases incorporating new features and fixes related to agent providers, E2B integration, and underlying agent infrastructure. Its key differentiator lies in its specialized focus on ACP and streamable HTTP for robust agent-computer interaction, contrasting with generic HTTP or RPC clients.
npm install acp-http-clientVerified import paths — ran on the pinned version, not inferred.
This quickstart demonstrates how to initialize the AcpHttpClient, define an agent's API interface, and make a basic JSON-RPC call to interact with a sandboxed agent's desktop and file system APIs.
Refer to the `sandbox-agent` repository's documentation or changelog for the correct agent installation script URL and ensure your deployed agent version is compatible with the client library's expected protocol.
Always pin to exact minor or patch versions (e.g., `0.4.2` or `^0.4.0`) to avoid unexpected behavior. Review the changelog for `0.5.0` (and subsequent major versions) thoroughly before upgrading to production environments.
Update error handling logic to account for potentially richer `AcpRpcError` messages and consider the implications of `defaultCwd` if you rely on specific working directories for agent commands. Test existing RPC error handling after upgrade.
Ensure you are using `import { AcpHttpClient } from 'acp-http-client';` for modern JavaScript/TypeScript environments. If forced to use CommonJS, ensure your build tool correctly transpiles ESM imports or look for a specific CJS build if available (though unlikely for this library).Verify that the `sandbox-agent` running matches the expected version by the `acp-http-client` library. Check the agent's logs for available RPC methods or ensure your agent's configuration properly registers the required capabilities.
Ensure the `sandbox-agent` is running and accessible at the `baseUrl` provided during `AcpHttpClient` initialization (e.g., `http://localhost:8080`). Check firewall rules and the agent's actual listening address and port.
No dependency data recorded yet.