Grok Build is now available in the AI SDK harness layer
Grok Build now plugs into AI SDK’s common HarnessAgent interface, letting agent applications add or swap this runtime without rewriting their orchestration code.
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.
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.
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.