Vercel AI SDK Harnesses Now Support Native Subscription Authentication
Shipped Sep 14 on Vercel's changelog: the AI SDK harness layer — the HarnessAgent abstraction Vercel introduced June 12 — now authenticates coding agents through their native subscriptions instead of requiring provider API keys.
What changed
Nine harness adapters support it today: Claude Code, Cline, Codex, Cursor, fx, GitHub Copilot, Grok Build, OpenCode, and Pi. Three auth modes control the behavior:
- direct — prefers explicit provider env credentials, falls back to any native subscription found on the host
- auto (default) — same, but only when no AI Gateway credentials are set
- ai-gateway — never reads native subscriptions; keeps billing on Vercel's metered gateway
The security detail buried in the note: when the sandbox supports it, the harness gets placeholder credentials and the real OAuth token is injected into outbound requests on the host. Tokens never enter the sandbox.
The economics
Here's what nobody said out loud. Anthropic's API rates for Sonnet 5 are $2/MTok input, $10/MTok output (verified on anthropic.com/pricing today). A Claude Pro subscription is $17/mo annual. That $17 buys roughly 1.7M output tokens at API rates — about what a single aggressive day of agent coding burns. Until now, running a harness through AI SDK pushed you toward metered billing. Today your existing flat-rate subscription just became a first-class credential.
Why a builder cares
Two stakes. First, cost: if you already pay for Claude Code or Copilot seats, your AI SDK agent workload can ride that flat rate — but note the default auto mode only falls back to subscriptions when AI Gateway credentials are absent, so nothing switches underneath you silently. Second, trust: the host-boundary token injection means a sandboxed agent that gets prompt-injected can't exfiltrate your OAuth session. That's the right architecture, and it's now the default.