update-harness-dependencies
SkillCloud & infraA skill that lets an AI agent update the primary SDK dependencies of harness packages in the Vercel AI monorepo. It runs pnpm update commands to bump each harness adapter's third-party SDK packages, including bridge dependencies with a minimum release age setting, and keeps matching SDK versions in example packages aligned.
Then ask your AI: use the update-harness-dependencies skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.
No other account needed.
Have the Vercel AI monorepo checked out with pnpm available.
What your AI can do with it
- Updates primary SDK dependencies of every packages/harness-* adapter
- Runs pnpm update with --latest --lockfile-only for each harness
- Updates bridge dependencies with a minimum release age setting
- Updates matching SDK versions in example packages
- Verifies dependency alignment with a verification script
Getting started
- Have the Vercel AI monorepo checked out with pnpm available.
- Confirm the minimum release age defined in pnpm-workspace.yaml.
- Run the pnpm --filter update commands for each harness package.
- Run the additional bridge dependency update commands with the minimum release age flag.
- Update matching SDK versions in example packages and run the verification script.
What this skill tells your AI
The instructions your AI receives, as published by vercel/ai in skills/update-harness-dependencies/SKILL.md and read by Ahel’s review.
Update the harness packages
The harness adapters are all the packages/harness-* packages. They each rely on one or more third-party packages for the respective harness's primary SDK. It is crucial to keep those dependencies up to date.
Below you find the instructions on how to update those packages to their latest versions, while adhering to the minimum release age defined in pnpm-workspace.yaml.
Update the harness dependency packages
Run the following commands to update each harness's primary SDK packages.
- For bridge harnesses (e.g. Claude Code), this will update the packages in
devDependencies, while the actual package versions used asdependenciesare only relevant to the harness's bridge itself. - For non-bridge harnesses (e.g. Pi), this will update the packages in
dependencies.
Run these commands exactly as below:
# ACP
pnpm --filter harness-acp update @agentclientprotocol/sdk @modelcontextprotocol/sdk --latest --lockfile-only
# Claude Code
pnpm --filter harness-claude-code update @anthropic-ai/claude-agent-sdk @modelcontextprotocol/sdk --latest --lockfile-only
# Cline
pnpm --filter harness-cline update @cline/agents @cline/core --latest --lockfile-only
# Codex
pnpm --filter harness-codex update @openai/codex --latest --lockfile-only
# Deep Agents
pnpm --filter harness-deepagents update @langchain/core @langchain/langgraph deepagents langchain langsmith --latest --lockfile-only
# GitHub Copilot
pnpm --filter harness-github-copilot update @github/copilot --latest --lockfile-only
# Grok Build
pnpm --filter harness-grok-build update @xai-official/grok --latest --lockfile-only
# OpenCode
pnpm --filter harness-opencode update @opencode-ai/sdk --latest --lockfile-only
# Pi
pnpm --filter harness-pi update @earendil-works/pi-coding-agent --latest --lockfile-only
For the bridge dependencies of bridge harnesses, you must additionally run the following commands. It is important to specify the config.minimumReleaseAge flag in accordance with what pnpm-workspace.yaml defines, because for these commands the --ignore-workspace flag is needed.
Run these commands exactly as below:
# ACP
pnpm --dir packages/harness-acp/src/v1/bridge update @agentclientprotocol/sdk @modelcontextprotocol/sdk --latest --ignore-workspace --config.minimumReleaseAge=4320
# Claude Code
pnpm --dir packages/harness-claude-code/src/bridge update @anthropic-ai/claude-agent-sdk @anthropic-ai/claude-code @modelcontextprotocol/sdk --latest --ignore-workspace --config.minimumReleaseAge=4320
# Codex
pnpm --dir packages/harness-codex/src/bridge update @openai/codex --latest --ignore-workspace --config.minimumReleaseAge=4320
# Deep Agents
pnpm --dir packages/harness-deepagents/src/bridge update @langchain/anthropic @langchain/core @langchain/langgraph deepagents langchain langsmith --latest --ignore-workspace --config.minimumReleaseAge=4320
# GitHub Copilot
pnpm --dir packages/harness-github-copilot/src/bridge update @github/copilot --latest --ignore-workspace --config.minimumReleaseAge=4320
# Grok Build
pnpm --dir packages/harness-grok-build/src/bridge update @agentclientprotocol/sdk @modelcontextprotocol/sdk @xai-official/grok --latest --ignore-workspace --config.minimumReleaseAge=4320
# OpenCode
pnpm --dir packages/harness-opencode/src/bridge update @opencode-ai/sdk opencode-ai --latest --ignore-workspace --config.minimumReleaseAge=4320
The following harness adapters use an unversioned installer script instead of an NPM package for their SDK / CLI and therefore can be ignored:
packages/harness-cursorpackages/harness-fx
Example dependencies
Check the package.json files in examples/harness-e2e-next and examples/harness-e2e-tui for any of the above SDKs they depend on. Those dependencies need to be updated to match the exact version used in the packages as well.
Update ACP and MCP SDKs everywhere
Find every harness package and bridge manifest that declares either SDK:
rg -n '"(@agentclientprotocol/sdk|@modelcontextprotocol/sdk)"' packages/harness-* --glob 'package.json'
For each matching workspace package manifest, update its declared SDKs with
pnpm --filter. Replace the placeholders with the harness workspace name and
the SDK package names found in that manifest:
pnpm --filter <harness-name> update <sdk-package>... --latest --lockfile-only
# Example
pnpm --filter harness-acp update @agentclientprotocol/sdk @modelcontextprotocol/sdk --latest --lockfile-only
For each matching bridge manifest, run pnpm --dir in the directory containing
that manifest:
pnpm --dir <bridge-directory> update <sdk-package>... --latest --ignore-workspace --config.minimumReleaseAge=4320
# Example
pnpm --dir packages/harness-acp/src/v1/bridge update @agentclientprotocol/sdk @modelcontextprotocol/sdk --latest --ignore-workspace --config.minimumReleaseAge=4320
Verification
Run the verification script to ensure all relevant dependency versions are aligned:
./tools/verify-harness-adapter-deps.mjs
If this script shows errors, you must address them, then rerun the verification script until it passes.
Signals
- GitHub stars
- 27k
- Forks
- 5k
- Last commit
- Oct 2026
Questions
- What does this skill update?
- It updates the primary SDK dependencies of harness packages, the bridge dependencies of bridge harnesses, and matching SDK versions in example packages.
- How does it handle the minimum release age?
- Bridge dependency commands pass config.minimumReleaseAge matching pnpm-workspace.yaml, since those commands need the --ignore-workspace flag.
- Which harness packages are covered?
- All packages/harness-* adapters, including ACP, Claude Code, Cline, Codex, Deep Agents, GitHub Copilot, Grok Build, OpenCode, and Pi.
- Does it update example packages too?
- Yes, it covers updating matching SDK versions in example packages and verifying alignment with a verification script.
Advanced
- Item type
- skill
- Key
update-harness-dependencies- Source
- github.com/vercel/ai
Related picks
Skill · thedaviddias
The pick for End-to-end testinge2e-environment-preflight
Skill · sno-ai
The pick for End-to-end testingsetup-ts-deep-modules
Skill · mattpocock
The pick for TypeScripttypescript-providers
Skill · composiohq
The pick for TypeScriptnode-deps-bumper
Skill · paulrberg
The pick for Nodenodejs-backend-patterns
Skill · wshobson
The pick for Node