VercelEngineering PostOfficial Source

GitHub Copilot is now available in the AI SDK harness layer

AI SDK now runs GitHub Copilot behind the same HarnessAgent interface as nine other coding harnesses, using an official adapter and ACP connection.

Vercel · Sep 10, 2026

Open Source Open Markdown Open JSON

Source Summary

The AI SDK harness layer adds GitHub Copilot through **@ai-sdk/harness-github-copilot**. It connects to HarnessAgent through **Agent Client Protocol (ACP)** and joins nine other named harnesses, including Claude Code, Codex, and Cursor.

Practical Implication

If your application already targets HarnessAgent, use the adapter boundary to test Copilot without rewriting application-level agent integration code. Keep agent-specific behavior behind that shared interface.

Agent-Ready Context

The AI SDK harness layer adds GitHub Copilot through **@ai-sdk/harness-github-copilot**. It connects to HarnessAgent through **Agent Client Protocol (ACP)** and joins nine other named harnesses, including Claude Code, Codex, and Cursor.

If your application already targets HarnessAgent, use the adapter boundary to test Copilot without rewriting application-level agent integration code. Keep agent-specific behavior behind that shared interface.

A common interface reduces switching cost but does not establish behavioral parity. The material gives no compatibility matrix, feature differences, or migration constraints across the supported harnesses.

Connected Context · Feed7 Judgment

Copilot’s addition expands HarnessAgent from a small compatibility idea into a broader runtime-selection surface and confirms ACP as the common boundary for another major coding agent. It lowers the application rewrite required to evaluate Copilot, but it also sharpens the unresolved question: shared protocol access is not evidence that permissions, events, controls, security, or task behavior match other harnesses.

Use ACP-compatible harnesses with the AI SDK harness layerThe ACP meta-adapter establishes the protocol-level portability path that the dedicated Copilot adapter uses, while also explaining why dedicated integrations may still matter for tighter behavior.Cursor is now available in the AI SDK harness layerCursor provides reinforcing evidence that multiple prominent coding runtimes can sit behind HarnessAgent, with the same warning that interface compatibility does not establish behavioral parity.Grok Build is now available in the AI SDK harness layerGrok Build further supports keeping orchestration at the shared HarnessAgent boundary, making Copilot an expansion of an existing multi-runtime pattern rather than a one-off integration.github/copilot-sdkThe direct Copilot SDK exposes permissions, authentication, billing, models, and packaging choices that remain agent-specific even when HarnessAgent removes application-level integration differences.

Context Map

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

Uncertainty

A common interface reduces switching cost but does not establish behavioral parity. The material gives no compatibility matrix, feature differences, or migration constraints across the supported harnesses.