docs.rs failed to build vtcode-acp-0.173.2
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Visit the last successful build:
vtcode-acp-0.128.4
vtcode-acp
vtcode-acp is the canonical ACP crate for VT Code.
Canonical surface is the SACP stdio agent in src/zed/ (StandardAcpAdapter,
ZedAcpAdapter, ZedAgent on upstream agent-client-protocol).
Legacy crate-internal HTTP stack (capabilities, client, client_v2, session,
messages, jsonrpc, transport HTTP /rpc+SSE types with date versions like
2025-01-01) is not the ACP stdio transport and must not be extended for new
protocol work. See AGENTS.md for the module map.
ACP (Agent Communication Protocol) support for VT Code.
This crate exposes both the ACP client library and the VT Code Zed bridge. Downstream crates should treat this as the canonical ACP entrypoint.
Public entrypoints
StandardAcpAdapterandZedAcpAdapterfor launching VT Code over ACP stdio (canonical)- Legacy HTTP helpers (
AcpClientV2,AcpClient) are crate-internal and not ACP stdio transports
API reference
See docs.rs/vtcode-acp.