Skip to content

feat(acp): bump claude-agent-acp to 0.73.0 - #634

Closed
Adam-Dalloul wants to merge 1 commit into
xintaofei:mainfrom
Adam-Dalloul:chore/bump-claude-agent-acp-0-73
Closed

feat(acp): bump claude-agent-acp to 0.73.0#634
Adam-Dalloul wants to merge 1 commit into
xintaofei:mainfrom
Adam-Dalloul:chore/bump-claude-agent-acp-0-73

Conversation

@Adam-Dalloul

Copy link
Copy Markdown
Contributor

Bumps the pinned Claude ACP adapter from 0.69.0 to 0.73.0.

Why: Anthropic ships new model availability through the bundled runtime. The raw model id claude-fable-5-1 is live, but the API rejects it on older runtimes with "Claude Code 2.1.247 does not support this model; version 2.1.251 or newer is required". The 0.69.0 pin bundles claude-agent-sdk 0.3.232 (runtime 2.1.232); 0.73.0 bundles 0.3.257 (runtime 2.1.257), so new Anthropic models surface in the model config option with no code change.

Verified live over ACP stdio: 0.73.0 boots, answers initialize, and session/new succeeds and advertises the model config option (Default / Opus 1M / Fable / Sonnet / Haiku).

Tarball-diffed all four releases in between. The per-version analysis (0.70.0 through 0.73.0) is in the registry comment above the pin, where it lives for every other version; comments that described the old pin's behavior (the option-level permission changes[] claim, the AIR tripwire enumeration, the title fallback) are updated in the same change.

Model availability ships in the bundled runtime: the live API rejects
claude-fable-5-1 below runtime 2.1.251 ("Claude Code 2.1.247 does not
support this model; version 2.1.251 or newer is required"), and the
0.69.0 pin's claude-agent-sdk 0.3.232 vendors 2.1.232. 0.73.0 pins
claude-agent-sdk 0.3.257 (runtime 2.1.257), so new Anthropic models
surface through the existing dynamic model config option with no code
change. Verified live over ACP stdio: 0.73.0 boots, answers initialize,
and session/new succeeds with the model option offering Default, Opus
1M, Fable, Sonnet and Haiku.

Tarball-diffed 0.69.0 through 0.73.0; the per-version analysis lives in
the registry comment like every earlier version. The short form: 0.70.0
is provider plumbing inside client-called requests codeg never sends;
0.71.0's five new session_update kinds are all gated on advertisements
codeg does not make (the AIR array stays exactly ["sessionFailure"],
which the no-catch-all SessionUpdate argument makes load-bearing), while
its ungated deltas land on surfaces codeg already consumes: generated
session titles on session_info_update.title, and the permission rebuild
that moves claude onto the request-level _meta.permission contract
hoist_request_permission_meta already forwards; 0.72.0 moves the ACP SDK
to 1.4.0 (TS API rename only, wire methods byte-identical) and adopts
per-model effort plus user_message_uuid result attribution; 0.73.0 is
the runtime bump alone (dist byte-identical to 0.72.0). engines.node
stays ">=22" across all four, so node_required holds.

Comments that stated the old pin's behavior are updated in the same
change: the codex 1.7.0 paragraph no longer claims claude still emits
option-level changes[], the hoist doc now names claude as a
request-level speaker, the AIR tripwire test enumerates all three
unwanted capabilities, and background_watch's title fallback describes
the 0.71.0 generation path.
@Adam-Dalloul

Copy link
Copy Markdown
Contributor Author

Superseded by main — closing is the right call.

6bc1c1f6 already moved the pin to 0.73.0 (registry.rs and the preflight test both read @agentclientprotocol/claude-agent-acp@0.73.0), and the 0.70.0–0.73.0 analysis on main is both fuller and more current than what this branch carries. Main also went further than this PR did: it actually adopts asyncTasks in build_client_capabilities, where this branch only documented it as not-adopted — so rebasing would re-assert a paragraph main has already disproved.

One small leftover, unrelated to the pin: the background_watch.rs module doc still says the adapter "only pulls the name at turn-end (maybeUpdateSessionTitle, claude-agent-acp 0.69.0)", which the session-titles.js note in registry.rs now contradicts. Happy to send that one-paragraph doc fix separately if it's wanted.

@Adam-Dalloul

Copy link
Copy Markdown
Contributor Author

Closing: 6bc1c1f already moved the pin to 0.73.0 with your own per-version analysis, and main goes further by actually adopting asyncTasks. Nothing left here worth rebasing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant