/update-harness-dependencies

name: update-harness-dependencies
description: Update the primary SDK dependencies of harness packages. Use when asked to update the harness SDKs or harness adapter dependencies.
metadata:
  internal: true

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
# 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/anthropic @langchain/core @langchain/langgraph deepagents langchain langsmith --latest --lockfile-only
# fx
pnpm --filter harness-fx update libfx --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 @agentclientprotocol/sdk @github/copilot @modelcontextprotocol/sdk --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 adapter uses an unversioned installer script instead of an NPM package for its CLI and therefore can be ignored:

• `packages/harness-cursor`

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

Align ACP npm-locked bridge manifests

ACP adapters that use an `npm-locked` source install their own bridge manifest instead of the `harness-acp` bridge manifest. `packages/harness-acp/src/v1/bridge/package.json` is the authoritative source for the bridge dependencies, and every `npm-locked` bridge manifest must declare each of its `dependencies` at the exact same version:

• `packages/harness-github-copilot/src/bridge/package.json`
• `packages/harness-grok-build/src/bridge/package.json`
• `examples/ai-functions/src/lib/codex-acp-bridge/package.json`
• `examples/harness-e2e-next/agent/harness/acp-codex/bridge/package.json`

After updating the `harness-acp` bridge manifest, copy its dependency versions into each of these manifests and regenerate their l