# fx is now available in the AI SDK harness layer

Source: [Vercel](https://vercel.com/changelog/fx-ai-sdk-harness-adapter)  
Feed7 permalink: https://feed7.dev/p/fx-ai-sdk-harness-adapter-0j0ujvp  
Published: 2026-08-31T06:00:00.000Z  
Trust: Official Source (official_source)

## Why Included

Vercel's AI SDK harness now runs fx through the same HarnessAgent API used for other coding agents, reducing the need for another bespoke integration.

## Source Summary

The AI SDK harness layer adds **fx** through the official **@ai-sdk/harness-fx** adapter. It connects over the Agent Client Protocol using @ai-sdk/harness-acp.

## Practical Implication

If your app already targets HarnessAgent, treat fx as another swappable agent backend rather than building an fx-specific execution path.

## Agent-Ready Context

The AI SDK harness layer adds **fx** through the official **@ai-sdk/harness-fx** adapter. It connects over the Agent Client Protocol using @ai-sdk/harness-acp.

If your app already targets HarnessAgent, treat fx as another swappable agent backend rather than building an fx-specific execution path.

The announcement describes interface compatibility, not behavioral parity, performance, or which fx capabilities survive the common abstraction.

## Connected Context

Feed7 judgment across 655 accumulated Signals:

fx expands HarnessAgent’s official backend set and confirms that ACP is serving as the portability boundary for coding runtimes. Applications already built to that interface gain another runtime choice without a separate execution path, but the adapter does not make fx behavior interchangeable with other agents; capability coverage, controls, security, and runtime semantics still require fx-specific validation.

- [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) — fx is a concrete implementation of the ACP portability path described by the meta-adapter, while retaining the same limitation that protocol compatibility does not guarantee precise runtime behavior.
- [Cursor is now available in the AI SDK harness layer](https://feed7.dev/p/cursor-ai-sdk-harness-adapter-0nbmzmh) — Both add an official runtime behind HarnessAgent, reinforcing a shared application boundary for agent selection while independently leaving behavioral parity unproven.
- [Cline is now available in the AI SDK harness layer](https://feed7.dev/p/cline-harness-adapter-1sv80a0) — Cline shows that adapters can have runtime-specific isolation boundaries, supporting the need to verify fx security and execution semantics rather than infer them from the common interface.

## Context Map

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

## Uncertainty

- The announcement describes interface compatibility, not behavioral parity, performance, or which fx capabilities survive the common abstraction.

## 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.