Tessl • The package manager for agent skills

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/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 adapter uses an unversioned installer script instead of an NPM package for its CLI and therefore can be ignored:

packages/harness-cursor

Update the pinned fx CLI version

The fx harness adapter pins the fx CLI release with FX_VERSION in packages/harness-fx/src/fx-harness.ts. To discover the latest release, run:

curl -fsSL https://releases.fx.sh/latest.txt

Update FX_VERSION to that version without a leading v, then run the fx harness tests:

pnpm --filter harness-fx test

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.

update-harness-dependencies