# Grok Build is now available in the AI SDK harness layer

Source: [Vercel](https://vercel.com/changelog/grok-build-harness-adapter)  
Feed7 permalink: https://feed7.dev/p/grok-build-harness-adapter-0edn2xt  
Published: 2026-08-13T00:00:00.000Z  
Trust: Official Source (official_source)

## Why Included

Grok Build now plugs into AI SDK’s common HarnessAgent interface, letting agent applications add or swap this runtime without rewriting their orchestration code.

## Source Summary

Vercel added **@ai-sdk/harness-grok-build**, an official Grok Build adapter for the AI SDK harness layer. It uses the same **HarnessAgent** interface as the other supported runtimes and is built on @ai-sdk/harness-acp.

## Practical Implication

If your application already targets HarnessAgent, evaluate Grok Build without creating another orchestration path. The supported set now covers **six harnesses**: Claude Code, Codex, Deep Agents, Grok Build, OpenCode, and Pi.

## Agent-Ready Context

Vercel added **@ai-sdk/harness-grok-build**, an official Grok Build adapter for the AI SDK harness layer. It uses the same **HarnessAgent** interface as the other supported runtimes and is built on @ai-sdk/harness-acp.

If your application already targets HarnessAgent, evaluate Grok Build without creating another orchestration path. The supported set now covers **six harnesses**: Claude Code, Codex, Deep Agents, Grok Build, OpenCode, and Pi.

The announcement describes interface compatibility, not behavioral parity. Because the adapter sits on ACP, confirm that Grok Build’s runtime-specific controls and events remain available for your workflow.

## Connected Context

Feed7 judgment across 461 accumulated Signals:

Grok Build turns the ACP portability path into another official HarnessAgent runtime, confirming that applications built around the shared interface can expand runtime choice without adding a separate orchestration path. It does not establish behavioral interchangeability: runtime-specific controls and events still need verification.

- [Use ACP-compatible harnesses with the AI SDK harness layer](https://feed7.dev/p/use-acp-compatible-harnesses-with-the-ai-sdk-harness-layer-105d5cg) — The Grok Build adapter is a concrete extension of the ACP meta-adapter approach, while its runtime-specific verification caveat reinforces ACP’s stated abstraction limits.

## Context Map

- Layer: tools
- Domains: coding
- Topics: coding-agents, agent-sdks, harness-engineering

## Uncertainty

- The announcement describes interface compatibility, not behavioral parity. Because the adapter sits on ACP, confirm that Grok Build’s runtime-specific controls and events remain available for your workflow.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.