VercelEngineering PostOfficial Source

Cursor is now available in the AI SDK harness layer

Vercel’s AI SDK can now run Cursor behind the same HarnessAgent interface as seven other coding agents, reducing application changes when swapping harnesses.

Vercel · Aug 27, 2026

Open Source Open Markdown Open JSON

Source Summary

The official **@ai-sdk/harness-cursor** adapter adds Cursor to Vercel’s AI SDK harness layer. It connects through **Agent Client Protocol (ACP)** and joins seven other supported coding-agent harnesses.

Practical Implication

Use **HarnessAgent** as the application boundary if you expect to test or switch among Cursor, Claude Code, Codex, Cline, Deep Agents, Grok Build, OpenCode, and Pi. That keeps agent selection out of the surrounding application code.

Agent-Ready Context

The official **@ai-sdk/harness-cursor** adapter adds Cursor to Vercel’s AI SDK harness layer. It connects through **Agent Client Protocol (ACP)** and joins seven other supported coding-agent harnesses.

Use **HarnessAgent** as the application boundary if you expect to test or switch among Cursor, Claude Code, Codex, Cline, Deep Agents, Grok Build, OpenCode, and Pi. That keeps agent selection out of the surrounding application code.

The announcement establishes interface compatibility, but does not compare feature parity, behavior, or portability across harnesses. Agent-specific capabilities may still require separate validation.

Connected Context · Feed7 Judgment

This makes Cursor an official runtime choice behind HarnessAgent, strengthening the case for keeping coding-agent selection at a shared application boundary. ACP connectivity supports integration portability, but the announcement narrows that claim to interface compatibility: runtime behavior, controls, security properties, and feature parity still require agent-specific testing.

Use ACP-compatible harnesses with the AI SDK harness layerThe ACP meta-adapter established protocol-level portability; Cursor’s dedicated adapter turns that path into an official integration while leaving behavioral equivalence unproven.Grok Build is now available in the AI SDK harness layerTogether they show HarnessAgent accumulating official runtime choices without separate orchestration paths, while both retain the need to validate runtime-specific events and controls.How Notion used the Cursor SDK to embed coding agentsNotion demonstrates direct product embedding through Cursor’s own SDK, whereas this adapter adds a more portable boundary for applications that expect to test or switch coding-agent runtimes.Governing agent autonomy with Auto-reviewCursor’s action-governance layer illustrates the kind of runtime-specific capability that common harness compatibility does not guarantee and must be validated separately.

Context Map

toolscoding#agent-sdks#coding-agents#harness-engineering

Uncertainty

The announcement establishes interface compatibility, but does not compare feature parity, behavior, or portability across harnesses. Agent-specific capabilities may still require separate validation.