Build ACP-Compatible Harnesses with AI SDK

๐กConnect new ACP-compatible coding agents to AI SDK without writing runtime-specific adapters.
โก 30-Second TL;DR
What Changed
The new @ai-sdk/harness-acp package wraps the ACP protocol instead of a single coding-agent runtime.
Why It Matters
This lowers the integration cost for emerging coding-agent runtimes that already support ACP, making them easier to adopt through a unified AI SDK interface. However, developers should evaluate ACP feature coverage before choosing it over a direct adapter.
What To Do Next
Review the ACP harness documentation and prototype an adapter with createACP for one ACP-compatible runtime that lacks a direct AI SDK adapter.
Key Points
- โขThe new @ai-sdk/harness-acp package wraps the ACP protocol instead of a single coding-agent runtime.
- โขDevelopers create an adapter with createACP, configure basic harness mapping, and pass it to HarnessAgent.
- โขDirect adapters remain recommended for Claude Code and Codex when tighter integration or better internal behavior exposure is needed.
๐ง Deep Insight
AI-generated analysis for this event.
๐ Enhanced Key Takeaways
- โขThe Agent Client Protocol (ACP) is an open-standard communication layer designed to decouple agentic runtimes from IDEs and development environments, facilitating interoperability across the AI ecosystem.
- โขThe @ai-sdk/harness-acp package leverages the Vercel AI SDK's modular architecture to allow developers to treat any ACP-compliant agent as a first-class citizen within the Vercel development workflow.
- โขBy utilizing the meta adapter pattern, the SDK reduces the maintenance burden for agent developers who previously had to write custom boilerplate for every supported IDE or runtime.
- โขThis release aligns with the broader industry trend of standardizing agent-to-tool communication, similar to how the Model Context Protocol (MCP) standardized data access for LLMs.
- โขThe implementation specifically addresses the 'adapter fragmentation' problem, where agent developers were forced to choose between limited platform support or high-effort custom integrations.
๐ Competitor Analysisโธ Show
| Feature | Vercel AI SDK (ACP) | LangChain Agent Tools | Microsoft AutoGen |
|---|---|---|---|
| Protocol Support | Native ACP | Custom/Proprietary | Proprietary/Custom |
| Integration Focus | Frontend/Web-Native | Backend/Orchestration | Multi-Agent Systems |
| Adapter Overhead | Low (Meta-Adapter) | High (Custom) | High (Custom) |
| Pricing | Open Source (MIT) | Open Source (MIT) | Open Source (Apache 2.0) |
๐ ๏ธ Technical Deep Dive
- The createACP function acts as a factory that initializes a connection to an ACP-compliant server, abstracting the underlying WebSocket or stdio transport layer.
- Harness mapping within the SDK translates ACP-specific tool definitions and agent capabilities into the standard AI SDK Tool and Agent interfaces.
- The meta adapter utilizes a dynamic dispatch mechanism to route requests from the HarnessAgent to the ACP server, ensuring that state synchronization and tool execution remain consistent with the SDK's lifecycle events.
- The implementation supports bi-directional communication, allowing the ACP server to trigger UI updates or request user input directly through the harness layer.
๐ฎ Future ImplicationsAI analysis grounded in cited sources
โณ Timeline
Weekly AI Recap
Read this week's curated digest of top AI events โ
๐Related Updates
AI-curated news aggregator. All content rights belong to original publishers.
Original source: Vercel News โ

