Vercel Adds Cline harness adapter to AI SDK’s Unified Interface.

Vercel is bringing Cline into its AI SDK harness layer, giving developers another established coding-agent runtime that can operate behind a common application interface. The new Cline harness adapter means teams can adopt or test the AI coding assistant without rewriting the surrounding integration each time they change runtimes.

The company announced the adapter in its changelog on August 18. The official package, @ai-sdk/harness-cline, was implemented in collaboration with the Cline team and works through AI SDK’s existing HarnessAgent interface.

That standardization is the main point. Rather than designing an application around Cline’s runtime specifically, developers can instantiate it as the harness supplied to HarnessAgent:

import { HarnessAgent } from '@ai-sdk/harness/agent';
import { cline } from '@ai-sdk/harness-cline';

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

For small product teams, agencies, and independent builders, the abstraction could make it easier to compare coding agents or replace one as requirements change. Application code can continue addressing the same interface while the harness layer handles the selected runtime.

The execution model has an important boundary. According to Vercel, Cline runs fully in the host process rather than being installed and executed inside a sandbox. It uses the sandbox as a remote filesystem and shell, which means Cline’s tools operate in the sandbox while the agent runtime itself remains in the host process.

No bridge process is installed in the sandbox. Vercel says this architecture is similar to its existing Pi harness. Developers evaluating the adapter should account for that distinction when reasoning about process isolation, permissions, and the infrastructure surrounding an agent session.

The adapter does not introduce a new coding agent or model. Instead, it packages Cline for the shared harness interface, allowing existing AI SDK applications to call it in the same general way as other supported runtimes. Vercel has published separate Cline harness documentation with setup guidance.

With Cline added, the AI SDK harness layer now supports seven runtimes:

• Claude Code
• Cline
• Codex
• Deep Agents
• Grok Build
• OpenCode
• Pi

The release follows Vercel’s earlier addition of Grok Build, which Create With previously covered. Together, the updates show Vercel positioning the harness layer as a compatibility boundary between agent-powered applications and the fast-changing selection of coding runtimes beneath them.

This matters because agent runtimes can differ in tool behavior, setup, execution architecture, and model support. A shared interface does not erase those differences, but it reduces how tightly an application must be coupled to any one runtime. Teams can potentially test alternatives while preserving orchestration code and the wider application structure.

There are limits to what Vercel disclosed in the short announcement. It did not specify separate pricing, plan requirements, or benchmark Cline against the other harnesses. Builders will still need to evaluate runtime behavior and operational constraints themselves. What the adapter provides is a supported integration point, developed with Cline’s team, inside an increasingly broad AI SDK agent layer.

What is Vercel Cline harness adapter?

The Cline harness adapter is the official @ai-sdk/harness-cline package for running Cline through Vercel AI SDK’s common HarnessAgent interface. It lets an application use Cline without creating a runtime-specific agent interface.

How does Cline use Vercel’s sandbox?

Cline runs in the host process and treats the sandbox as a remote filesystem and shell. Its tools operate inside the sandbox, but no bridge process or complete Cline runtime is installed there.

When is the Cline harness adapter available, and what does it cost?

Vercel announced the adapter as available on August 18, 2026 and linked to its setup documentation. The changelog does not specify separate pricing or a required Vercel plan.