Skip to content

Version Packages - #40

Merged
Harold Hunt (huntharo) merged 1 commit into
mainfrom
changeset-release/main
Sep 18, 2026
Merged

Harold Hunt (huntharo) merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@pwrdrvr/agent-acp@0.16.1

Patch Changes

  • 384493a: Make a low-effort reasoning request actually lower an ACP agent's thinking when that agent offers only graded levels, and choose the level from the session's own option menu rather than whichever session wrote last.

    Three fixes, which only work together. Each is guarded by its own test.

    Graded thought levels. reasoningValueForThoughtLevel mapped a low-effort token only onto an off-like value (off / none / disabled / no). An agent that offers graded levels and no off got nothing. That covers Kimi's K3, whose thinking option is low / high / max / on. A low-effort token now falls back to the low level (also minimal / min / minimum) when there is no off. Off still wins where both exist, and a value that already read as on (say, "On (minimal budget)") still reads as on. Before this, reasoning: "low" changed nothing on any Kimi model: K2.7 Coding offers only on, and K3's low never matched.

    Per-session option menus. A pooled AcpAgentClient serves many sessions, but it kept one client-wide runtimeCapabilities, overwritten by every session/new, option write, and load. applyReasoning(threadId, …) and setModel(threadId, …) read that shared snapshot. Once sessions can be on different models (0.16.0), and the model decides which thought levels exist, a session could be matched against another session's menu. For example, an enrichment on K3 with a chat thread opened after it on K2.7 got a low request matched against [on], and no write was sent. The reverse sent thinking=low to a K2.7 session, which the agent refuses. Each session now keeps its own menus, taken from its session/new / session/load result and refreshed by its own option writes. setModel, applyReasoning, and a session's runtime-capability notifications read those. A session's menus are built on what initialize reported, never on the client-wide snapshot. Before, a new session inherited any menu its session/new omitted from whichever session wrote last, current values included, and could skip a write it believed was already applied. The client-wide snapshot remains for agent-level questions (session load, MCP transport support). An option write's reply now updates the session's runtime state as well as its menus, so options the write reshaped report where the agent actually put them.

    config_option_update in the ACP 1.3 shape. ACP 1.3 defines this update as the full configOptions set. The parser read only a single changed option (update.configOption), so the spec shape was dropped entirely. Kimi emits it after every model change, and it is the only report session/set_model gives (that call answers {}). The full set now replaces the session's menus and current values, including currentModelId, however the update is keyed (sessionUpdate, session_update, kind, type). That means a model the agent changed no longer loses to a stale requested one in thread_settings.

    Measured against Kimi Code CLI 2.0.0, with two sessions on one client and the prompt refused locally so no model turn ran: startThread({ model: "kimi-code/k3" }), then a chat thread on the default model, then startTurn({ reasoning: "low" }) on the first. 0.16.0 sends no thinking write. This change sends thinking=low, and Kimi's reply confirms model=kimi-code/k3 thinking=low.

@huntharo
Harold Hunt (huntharo) merged commit 9d73a12 into main Sep 18, 2026
2 checks passed
@huntharo
Harold Hunt (huntharo) deleted the changeset-release/main branch September 18, 2026 20:13
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