Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding

Claude Agent ACP 0.103: ACP v2 breaks deep imports

Written November 10, 2026

Claude Agent ACP 0.103 moves to ACP v2 and removes the v1 bridge. Anything importing from the package's deep dist/ paths breaks on upgrade — and the fix is a small import change, if you know where to look.

The problem

A client or IDE integration built on Claude Agent ACP imports functions from deep inside the package — paths under dist/ that were never part of the public surface. Version 0.103.0, released November 10, 2026, turns those imports into failures, and removes the v1 bridge that let v1-only clients keep working. The upgrade is safe for code that only uses the documented exports, and a breaking change for code that reaches further in.

What 0.103.0 changes

The 0.103.0 release serves ACP v2 with a direct v2 agent and removes the v1 bridge. The breaking change is explicit: deep imports of dist/ files fail with ERR_PACKAGE_PATH_NOT_EXPORTED, and lib.ts exports only serveAcp, AUTH_STATUS_UPDATE_METHOD, and their types. The same release gives subagent checklists their own plan ID, and refactors the exports so only lib.ts is exported. Two same-day follow-ups landed alongside it: 0.104.0 implements the ACP auth/status request next to _auth/status_update and offers Anthropic Console login in remote environments, and 0.104.1 carries the auth detail in the ACP account label, distinguishes Ultra from Max in auth status, and updates to the Claude Agent SDK 0.3.322.

The v2 switch is not optional. With the bridge removed, a client speaking only v1 has no path forward on this package — it must move to v2. The release notes treat that as a done decision, not a deprecation with a grace period.

What to change before you upgrade

Search your code for imports reaching into the package's dist/ paths and replace them with the lib.ts exports: serveAcp and AUTH_STATUS_UPDATE_METHOD, plus their types. Anything else you were importing from deep paths has no replacement in the new export list — that code needs rewriting against the v2 surface, not a renamed import. If your client speaks ACP v1, move it to v2 before upgrading; the bridge that used to translate is gone. Then take 0.104.1, not 0.103.0, as the target version: it carries the same v2 switch plus the auth-status fixes, including the Ultra-versus-Max distinction in the account label.

What it does not change

The breaking change is about imports and protocol version, not about how sessions run. Nothing in the 0.103.0 notes changes session handling, model selection, or the agent's behaviour once a session is open. The auth/status additions in 0.104.0 are new capabilities — a client that does not ask for auth status sees no difference. And the version numbers are close together for a reason: 0.103.0, 0.104.0, and 0.104.1 all shipped November 10, 2026, so a version pinned to 0.102.0 or earlier is one day behind, not one release behind.

Limits

Related playbooks

Sources

Back to: Coding playbooks hub · Also: Claude Agent ACP 0.101: idle compaction before the cache expires · The MCP spec kills sessions: stateless servers · Claude Code 2.1.321: Fable 5.2 is default