How do I use the update commands?

You simply run the provided bash commands for each specific harness to update its SDK dependencies.

What if I encounter errors after running the verification script?

You will need to address the errors indicated by the verification script and rerun it until all dependencies are aligned.

Is this skill suitable for all types of projects?

This skill is specifically designed for projects that utilize harness packages and may not be applicable for other types of projects.

Can I customize the update commands?

While the commands are predefined, you can modify them as needed to fit your specific project requirements.

Update Harness Dependencies

Name: Update Harness Dependencies
Availability: InStock
Author: vercel

OfficialFree

Keep your harness SDKs up to date effortlessly.

by vercel26.1k stars on vercel/ai

1 views

Updated Aug 10, 2026

Get this skill

Free · Opens the source repo

What Update Harness Dependencies does

The Update Harness Dependencies skill is designed to streamline the process of updating SDK dependencies for various harness packages. These packages, located in the packages/harness-* directory, rely on third-party SDKs that must be kept current to ensure compatibility and performance. This skill provides a set of predefined commands that allow developers to quickly update these dependencies while adhering to the minimum release age specified in the pnpm-workspace.yaml file.

When using this skill, developers can execute specific commands to update dependencies for different harnesses, such as Claude Code, Codex, and Pi. Each command targets the relevant SDKs, ensuring that the correct versions are updated in either devDependencies or dependencies, depending on whether the harness is a bridge or non-bridge type. This precision helps maintain the integrity of the development environment and reduces the risk of compatibility issues.

In addition to updating the main dependencies, the skill also includes commands for updating bridge dependencies, which require special consideration of the minimum release age. By following the provided commands, developers can ensure that all relevant packages are aligned and functioning as expected. After updating, a verification script is included to confirm that all dependency versions are consistent, allowing for a smooth development process without manual checks.

This skill is particularly useful for developers working with AI agents and their respective harnesses, as it automates the tedious task of keeping SDKs up to date, ultimately enhancing productivity and reducing potential errors in the development workflow.

When to use it

Use this skill when you need to update SDK dependencies for harness packages in your project.

When not to use it

This skill is not suitable for projects that do not utilize harness packages or require custom dependency management workflows.

What you can build with it

Updating SDKs for Claude Code

Run the specific commands to update the SDK dependencies for the Claude Code harness, ensuring compatibility.

Maintaining Dependencies for Codex

Use the skill to keep Codex SDK dependencies current, preventing potential integration issues.

Verifying Dependency Alignment

After updating, execute the verification script to confirm that all harness adapter dependencies are correctly aligned.

How to install Update Harness Dependencies

View source

1. Install with the skills CLI

npx skills add vercel/ai/update-harness-dependencies --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by vercel

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 as dependencies are 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
# Codex
pnpm --filter harness-codex update @openai/codex-sdk --latest --lockfile-only
# Deep Agents
pnpm --filter harness-deepagents update @langchain/core @langchain/langgraph deepagents langchain langsmith --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-sdk --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
# 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

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.

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.

Frequently asked questions about Update Harness Dependencies

Similar skills

Turborepo

Optimized build system for JavaScript/TypeScript monorepos.

Azure Pipelines Validation

Streamline your Azure DevOps pipeline changes locally.

Azure Developer CLI

Streamline your Azure project workflows with best practices.

Azure Container Registry CLI

Manage Azure Container Registry resources with ease.

Aspire

Build and orchestrate polyglot distributed applications seamlessly.

Vercel CLI

Manage and deploy Vercel projects from the command line.