{
  "schema_version": "1.1",
  "id": "archive:https://vercel.com/changelog/grok-build-harness-adapter",
  "slug": "grok-build-harness-adapter-0edn2xt",
  "url": "https://feed7.dev/p/grok-build-harness-adapter-0edn2xt",
  "title": "Grok Build is now available in the AI SDK harness layer",
  "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.",
  "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_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.\n\nIf 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.\n\nThe 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.",
  "source": {
    "name": "Vercel",
    "url": "https://vercel.com/changelog/grok-build-harness-adapter",
    "published_at": "2026-08-13T00:00:00.000Z"
  },
  "source_class": "blog_post",
  "content_type": "Engineering Post",
  "layer": "tools",
  "domains": [
    "coding"
  ],
  "topics": [
    "coding-agents",
    "agent-sdks",
    "harness-engineering"
  ],
  "verification": {
    "status": "official_source",
    "label": "Official Source",
    "method": "source_feed",
    "verified_at": null
  },
  "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."
  ],
  "connected_context": {
    "meaning": "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.",
    "corpus_size": 461,
    "generated_at": "2026-08-15T10:04:32.145Z",
    "connections": [
      {
        "title": "Use ACP-compatible harnesses with the AI SDK harness layer",
        "source_name": "Vercel",
        "source_url": "https://vercel.com/changelog/use-acp-compatible-harnesses-with-the-ai-sdk-harness-layer",
        "feed7_url": "https://feed7.dev/p/use-acp-compatible-harnesses-with-the-ai-sdk-harness-layer-105d5cg",
        "reason": "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."
      }
    ]
  },
  "lifecycle": "Current",
  "published_at": "2026-08-13T00:00:00.000Z",
  "modified_at": "2026-08-13T00:00:00.000Z",
  "supersedes": [],
  "expires_at": null,
  "formats": {
    "html": "https://feed7.dev/p/grok-build-harness-adapter-0edn2xt",
    "json": "https://feed7.dev/p/grok-build-harness-adapter-0edn2xt.json",
    "markdown": "https://feed7.dev/p/grok-build-harness-adapter-0edn2xt.md"
  }
}