chore(acp): bump codebuddy, dimcode, grok and kilo registry pins to probed versions - #909
Merged
Merged
Conversation
kaizhou-lab
added a commit
that referenced
this pull request
Aug 22, 2026
…ons (#921) ## Summary Scheduled ACP Registry version sync. Three npx pins drifted since #909, each backed by a fresh serial ACP probe of the exact pinned version. Lock-only change — three lines; no metadata, migration, or entrypoint edits, and no lock-derived test assertion embeds any of these versions. | backend | package | old → new | initialize | session/new | |---|---|---|---|---| | dimcode | `dimcode` | 0.3.17 → **0.3.18** | ok (agentInfo version 0.3.18) | auth required (`-32000`, "Provider credentials are required") | | grok | `@xai-official/grok` | 1.0.7 → **1.0.8** | ok (protocolVersion 1) | auth required (`-32000`, "no auth method id provided") | | nova | `@compass-ai/nova` | 1.1.35 → **1.1.37** | ok (protocolVersion 1) | config required (`-32000`, "Click Nova Setup to configure your API keys", advertising `kore-terminal-auth`) | All three meet the release-lock criterion: `initialize` succeeds and `session/new` returns a clearly classified authentication/configuration requirement. Probes ran serially with no inherited HOME or credentials. Nova skips 1.1.36 — the Registry advertises 1.1.37 directly, and that is the version probed and pinned. Derived-assertion check: each outgoing version (`0.3.17`, `1.0.7`, `1.1.35`) was grepped directly across `crates/**/*.rs` — none appears, so this is a pure lock change. That per-version scan replaces the package-name regex used before #909, where a `--package`-form literal split across lines slipped through and broke CI. The other 8 Registry-pinned packages (autohand, codebuddy, deepagents, dirac, glm-acp-agent, kilo, pi, sigit) match the snapshot exactly. Package names and entrypoint args are unchanged for all 11. Drifted but not upgraded: none. `mimo-code` remains the one non-Registry builtin (no `registry_json_id`), excluded from drift reconciliation. dimcode continues to self-report `agentInfo.title` as "DimAgent" and nova as `kore-cli` `1.0.0`; both public listings are unchanged, so no metadata follows — the standing observations from #837/#848. ## Registry snapshot - Audit pinned to release tag [`v2026.08.22-07e9ed7`](https://cdn.agentclientprotocol.com/registry/v1/v2026.08.22-07e9ed7/registry.json) of `agentclientprotocol/registry`, fetched via the versioned CDN path for reproducibility. - No newly listed and no delisted agents versus the 39-id baseline (which includes `antigravity-acp`, listed 2026-08-21 and deferred as binary-only). ## Validation - `just migration-check` — pass - `just lint-fix` (`cargo fix` + `clippy --fix --workspace -D warnings`) — clean - `just fmt` — clean - **Local `cargo nextest` intentionally skipped, by standing policy for lock-only bumps** (established 2026-08-11). The Test check on this PR is the authority for this change: the merge decision depends on CI rather than the local run, and this host's load only manufactures timeout-shaped test failures, which nothing in the local steps above is subject to. ## Logging No logging changes: lock-only version bumps; existing startup/session error paths already identify a failing agent by backend. Co-authored-by: zk <>
kaizhou-lab
added a commit
that referenced
this pull request
Aug 24, 2026
…ns (#931) ## Summary Scheduled ACP Registry version sync. Two npx pins drifted since #921, each backed by a fresh serial ACP probe of the exact pinned version. The diff is the lock file plus the one lock-derived test assertion that embeds codebuddy's version. | backend | package | old → new | initialize | session/new | |---|---|---|---|---| | codebuddy | `@tencent-ai/codebuddy-code` | 2.137.1 → **2.138.0** | ok (protocolVersion 1) | auth required (`-32000`, category `auth`) | | dimcode | `dimcode` | 0.3.18 → **0.3.19** | ok (agentInfo version 0.3.19) | auth required (`-32000`, "Provider credentials are required") | Both meet the release-lock criterion: `initialize` succeeds and `session/new` returns a clearly classified authentication requirement. Probes ran serially with no inherited HOME or credentials. codebuddy's `--acp` entrypoint is unchanged across the minor bump. **Derived assertion updated:** `registry_npx_lock.rs` pins codebuddy's exact version inside a `--package`-form argument list, so it moves with the lock — `2.137.1` → `2.138.0`. This is the same assertion that broke CI in #909 when a package-name regex missed it; the per-version scan introduced afterwards (grep each OUTGOING version across `crates/**/*.rs`) caught it before push this time. dimcode's `0.3.18` has no such assertion. `npx_cache_repair.rs` keeps its own version literals: those are cache-path hash fixtures, not lock assertions, and changing them would break their hash expectations. The other 9 Registry-pinned packages (autohand, deepagents, dirac, glm-acp-agent, grok, kilo, nova, pi, sigit) match the snapshot exactly. Package names and entrypoint args are unchanged for all 11. Drifted but not upgraded: none. `mimo-code` remains the one non-Registry builtin (no `registry_json_id`), excluded from drift reconciliation. dimcode continues to self-report `agentInfo.title` as "DimAgent" against a public listing that says "DimCode" — the standing observation since #814; no metadata change. ## Registry snapshot - Audit pinned to release tag [`v2026.08.24-06dfed0`](https://cdn.agentclientprotocol.com/registry/v1/v2026.08.24-06dfed0/registry.json) of `agentclientprotocol/registry`, fetched via the versioned CDN path for reproducibility. - No newly listed and no delisted agents versus the 39-id baseline (which includes `antigravity-acp`, deferred as binary-only since 2026-08-21). ## Validation - `just migration-check` — pass - `just lint-fix` (`cargo fix` + `clippy --fix --workspace -D warnings`) — clean - `just fmt` — clean - **Local `cargo nextest` intentionally skipped, by standing policy for lock-only bumps** (established 2026-08-11). The Test check on this PR is the authority for this change: the merge decision depends on CI rather than the local run, and this host's load only manufactures timeout-shaped test failures, which nothing in the local steps above is subject to. ## Logging No logging changes: lock version bumps plus one test assertion; existing startup/session error paths already identify a failing agent by backend. --------- Co-authored-by: zk <>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Scheduled ACP Registry version sync. Four npx pins drifted since #880, each backed by a fresh serial ACP probe of the exact pinned version. Lock-only change — four lines; no metadata, migration, or entrypoint edits, and no lock-derived test assertion embeds any of these versions.
@tencent-ai/codebuddy-code-32000, categoryauth)dimcode-32000, "Provider credentials are required")@xai-official/grok-32000, "no auth method id provided")@kilocode/cliAll four meet the release-lock criterion:
initializesucceeds andsession/neweither succeeds or returns a clearly classified authentication requirement. Probes ran serially with no inherited HOME or credentials.codebuddy jumps 31 patch releases (2.106.7 → 2.137.1); the
--acpentrypoint is unchanged and the handshake behaves as before (initialize ok, auth-required classification), so this stays a lock-only bump.The other 7 Registry-pinned packages (autohand, deepagents, dirac, glm-acp-agent, nova, pi, sigit) match the snapshot exactly. Package names and entrypoint args are unchanged for all 11. Drifted but not upgraded: none.
mimo-coderemains the one non-Registry builtin (noregistry_json_id), excluded from drift reconciliation.dimcode continues to self-report
agentInfo.titleas "DimAgent" while the public listing says "DimCode" (dimcode.devunchanged) — the standing observation carried since #814; no metadata change.A new agent was listed this cycle but is out of scope for this PR:
antigravity-acp(Google Antigravity) appeared on the Registry. It ships binary-only (Google-hostedagy_acp_serverarchives, no npx distribution), so per the skill's constraints it is not auto-integrated here and is recorded as reported-pending. Note that AionCore already supports the Antigravity product through the user-installedagydirect-CLI path (migration 034); this Registry entry is a separate downloadable ACP-server binary — an alternative transport for the same product, not a missing agent. Full detail is in the run report, not this lock PR.Registry snapshot
v2026.08.20-67c9d25ofagentclientprotocol/registry, fetched via the versioned CDN path for reproducibility.antigravity-acpadded, see above); no delisted agents.Validation
just migration-check— passjust lint-fix(cargo fix+clippy --fix --workspace -D warnings) — cleanjust fmt— cleancargo nextestintentionally skipped, by standing policy for lock-only bumps (established 2026-08-11; nine prior lock PRs merged green under it). The Test check on this PR is the authority for this change: the merge decision depends on CI rather than the local run, and this host's load only manufactures timeout-shaped test failures, which nothing in the local steps above is subject to.Logging
No logging changes: lock-only version bumps; existing startup/session error paths already identify a failing agent by backend.