# Cline is now available in the AI SDK harness layer

Source: [Vercel](https://vercel.com/changelog/cline-harness-adapter)  
Feed7 permalink: https://feed7.dev/p/cline-harness-adapter-1sv80a0  
Published: 2026-08-18T00:00:00.000Z  
Trust: Official Source (official_source)

## Why Included

Vercel’s AI SDK harness now runs Cline behind the same interface as six other coding-agent runtimes, while keeping Cline in the host and sandboxing only its tools.

## Source Summary

The official **@ai-sdk/harness-cline** adapter runs Cline through the shared HarnessAgent interface. The harness layer now supports **seven runtimes**, including Claude Code, Codex, Cline, OpenCode, Pi, Deep Agents, and Grok Build.

## Practical Implication

Builders maintaining agent products can put Cline behind the existing interface and compare or switch runtimes without rewriting application integration code. Review trust boundaries before assuming the entire runtime is isolated.

## Agent-Ready Context

The official **@ai-sdk/harness-cline** adapter runs Cline through the shared HarnessAgent interface. The harness layer now supports **seven runtimes**, including Claude Code, Codex, Cline, OpenCode, Pi, Deep Agents, and Grok Build.

Builders maintaining agent products can put Cline behind the existing interface and compare or switch runtimes without rewriting application integration code. Review trust boundaries before assuming the entire runtime is isolated.

Cline itself runs in the **host process**; only its filesystem and shell tools operate in the sandbox, with no bridge installed there. The material does not specify behavioral parity between supported runtimes.

## Connected Context

Feed7 judgment across 525 accumulated Signals:

This confirms that HarnessAgent is becoming a practical runtime-selection layer, adding Cline as a seventh official option without requiring another application integration. It does not establish behavioral interchangeability, and it sharpens the security boundary: Cline remains in the host process while only filesystem and shell tools are sandboxed, so adopting the adapter must not be treated as full runtime isolation.

- [Grok Build is now available in the AI SDK harness layer](https://feed7.dev/p/grok-build-harness-adapter-0edn2xt) — Both official adapters reinforce that one HarnessAgent integration can add or swap coding runtimes, while neither establishes parity in runtime-specific behavior.
- [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) — The Cline adapter complements the generic ACP path: ACP broadens compatibility, while a dedicated adapter provides an official integration without proving identical controls or events.
- [Vercel AI Gateway and Vercel Sandbox now available on Hermes Agent](https://feed7.dev/p/vercel-ai-gateway-and-vercel-sandbox-now-available-on-hermes-agent-04gyfsv) — Both separate where the agent runs from where commands execute, reinforcing that sandboxed tools do not automatically mean the whole agent runtime is isolated.
- [github/copilot-sdk](https://feed7.dev/p/copilot-sdk-0vwjjou) — Copilot SDK exposes another embeddable coding runtime, but HarnessAgent targets cross-runtime application portability; both still leave permissions, authentication, and process boundaries as product responsibilities.

## Context Map

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

## Uncertainty

- Cline itself runs in the **host process**; only its filesystem and shell tools operate in the sandbox, with no bridge installed there. The material does not specify behavioral parity between supported runtimes.

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