Ciying AI Directory
AI DirectorySkills
中文
Ciying AI Directory

Vercel AI SDK Harness Dependencies: Check a Claude Bridge Update

Review which manifests and lockfiles change when Vercel AI SDK maintainers update a Claude Code harness bridge dependency.

中文

Setup for Codex (AI SDK contributor workflow)

Codex in a local AI SDK contributor checkout with the workspace's declared Node.js and pnpm versions. This example compares fictional manifests offline.

  1. Open a scratch checkout of Vercel AI SDK at the GitHub revision below. Copy the full `skills/update-harness-dependencies/` folder into `.agents/skills/update-harness-dependencies/` and start a fresh Codex session.
  2. This is an internal contributor guide. Use it only with the AI SDK source layout and a disposable local checkout.
  3. Read the guide's bridge-specific commands and the workspace minimum release age. Check both the wrapper and bridge lockfiles according to the package layout.

Example task

Review a toy Claude Code harness plan. Its wrapper devDependency changes version 1.2.0 to 1.3.0, while the runtime bridge keeps 1.2.0 by mistake. Under the fixture's rule that both must target 1.3.0, identify what still needs updating and how to validate the plan.

Expected result

The review flags the stale bridge runtime pin and lockfile. It states that the wrapper-only diff cannot upgrade the runtime side, and calls for both resolved versions to be checked.

Upstream documentation

Original SKILL.md on GitHub · Apache-2.0 license · Source reviewed

Frequently asked question

Do Vercel AI SDK bridge and host adapters use the same lockfile layout?

Their runtime dependencies can live in different manifests. Follow the specific adapter instructions and inspect the lockfiles touched by the actual change.