Vercel Adds Grok Build to AI SDK Harness Layer.

Vercel is bringing Grok Build into its AI SDK harness layer, giving developers a standardized way to add xAI’s coding-agent runtime to applications without building a bespoke integration.

The company announced the adapter on August 13. Grok Build now runs through the same HarnessAgent interface used by other supported agent harnesses, which means teams can adopt or test the runtime while keeping their surrounding application code largely consistent.

That is the practical value of the release. Rather than treating every coding agent as a separate integration, Vercel’s harness layer provides a common interface between an application and the runtime carrying out coding tasks. Developers can switch supported runtimes without rewriting the parts of their product responsible for invoking and managing the agent.

The official package is @ai-sdk/harness-grok-build. Vercel says it is built on top of the company’s Agent Client Protocol adapter, distributed as @ai-sdk/harness-acp.

A basic implementation imports HarnessAgent from the core harness package and grokBuild from the new adapter:

import { HarnessAgent } from '@ai-sdk/harness/agent';
import { grokBuild } from '@ai-sdk/harness-grok-build';

const agent = new HarnessAgent({
  harness: grokBuild,
});

The small code surface is deliberate. Grok Build is passed into HarnessAgent as the selected harness, while the application continues interacting with the agent through Vercel’s shared abstraction.

Underneath, the ACP-based implementation is also significant. Agent Client Protocol is intended to standardize communication between coding-agent clients and runtimes. By building the Grok Build package on its existing ACP adapter, Vercel is extending its SDK through a reusable protocol layer rather than introducing a one-off provider interface.

For small teams, that could reduce the cost of evaluating coding agents. A builder may want to compare output quality, reliability or workflow fit across runtimes, but provider-specific orchestration code can make those tests disproportionately expensive. A shared interface does not eliminate differences in model behavior or configuration, but it can reduce the amount of application infrastructure that must change during a trial.

The release also clarifies the distinction between Vercel’s AI SDK harness layer and its AI Gateway. The harness layer is focused on running established coding-agent runtimes through a common programming interface. AI Gateway provides centralized model access and operational features such as request traces, fallbacks and spend tracking, including the recently added Gemini 3.7 Flash integration.

Grok Build’s arrival fits Vercel’s broader push to make AI application infrastructure more modular. Teams can build around HarnessAgent, select Grok Build as the runtime, and retain a clearer path to changing runtimes later. That portability matters most for products that expose coding agents to customers or automate development work internally, where coupling the entire application to one agent implementation can become a maintenance problem.

There are limits to what Vercel disclosed. The changelog does not specify separate pricing, plan requirements or detailed deployment prerequisites for the Grok Build adapter. It also does not claim that all harness runtimes behave identically. The standardized interface simplifies integration, but teams will still need to evaluate Grok Build’s capabilities and operational requirements for their particular workflow.

What is Vercel Grok Build?

Grok Build is an xAI coding-agent runtime that can now be used through Vercel’s AI SDK harness layer. The official adapter lets developers provide Grok Build to the shared HarnessAgent interface instead of creating a separate runtime integration.

Which package adds Grok Build to the AI SDK?

Developers use @ai-sdk/harness-grok-build alongside @ai-sdk/harness. Vercel says the Grok Build adapter is implemented on top of its existing @ai-sdk/harness-acp package.

Does Grok Build require a specific Vercel plan?

Vercel’s announcement does not identify a required plan or provide separate pricing for the adapter. Developers should consult the current Grok Build harness documentation and relevant provider terms before deploying it in production.