Skip to content

graff — a fast agentic coding harness in Zig: multi-provider, MCP, workflows, DGM evolution loop, TS/Python SDKs

Python

Release v0.0.302.6

justrach47cbf31e867e
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 443dcabd..bad39f64 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -10,6 +10,24 @@ The release workflow uses a tag's section here as its release notes (a
hand-written `docs/releases/<tag>.md` wins if present), so keeping this file
current is part of cutting a release.
+## v0.0.302.6
+
+### ACP
+
+- `ask_user` no longer freezes clients that cannot show a question. A client that advertises `clientCapabilities.elicitation.form` gets a standard `elicitation/create` form request; the desktop app opts in to Graff's own question update; any other client gets an immediate result so the model continues instead of waiting for an answer that cannot arrive.
+- A running subagent streams its work onto the parent's tool call as ordinary `tool_call_update` content: a bounded log of its tool calls, failures and the tail of its message. Any ACP client shows it without changes. `GRAFF_ACP_SUBAGENT_PROGRESS=0` turns it off.
+- ACP v2 draft preview: with `GRAFF_ACP_V2=1` and a client that asks for protocol version 2, prompts are acknowledged with a `messageId` on insertion and the outcome arrives as `state_update`, chunks carry message IDs, tool rows are created by `tool_call_update`, and `session/close` and `session/resume` are available. Every other connection keeps v1 unchanged.
+- An empty JSON-RPC result (for example `session/cancel` with an id) is now `{}` rather than `[]`.
+
+### Agents on one device
+
+- `graff peer list|send|inbox|read` lets any agent on the machine, not only graff sessions, list live agents, post to a worktree room, or send a direct message.
+
+### Logins
+
+- `graff keys` syncs provider logins between your devices through an end-to-end encrypted vault: `status`, `enable`, `devices`, `approve`, `remove`, `push`, `pull`, `put` and `get`. Rotating logins refresh under a vault lease so two devices cannot race a refresh.
+- Kimi requests identify graff as the platform, and Kimi console keys are billed as plan usage.
+
## v0.0.302.5
### Session and transport fixes
diff --git a/docs/releases/v0.0.302.6.md b/docs/releases/v0.0.302.6.md
new file mode 100644
index 00000000..7147e385
--- /dev/null
+++ b/docs/releases/v0.0.302.6.md
@@ -0,0 +1,65 @@
+# Codegraff v0.0.302.6
+
+This release stops `ask_user` from freezing ACP clients, shows what subagents
+are doing in any ACP client, previews the ACP v2 draft, lets any agent on the
+machine message graff sessions, and syncs provider logins between devices.
+
+## Questions over ACP
+
+`ask_user` used to send Graff's own question update to every ACP client and
+then wait for an answer. A client that could not show the question displayed
+nothing, and the turn stayed blocked until the user cancelled it.
+
+Now a client that advertises `clientCapabilities.elicitation.form` receives a
+standard `elicitation/create` form request with one required `answer` field,
+listing the model's choices when it offered some. `accept` returns the answer;
+`decline` and `cancel` end the question. The desktop app opts in to Graff's
+own question update. Any other client gets an immediate result, so the model
+makes a reasonable assumption or asks in its reply instead of waiting.
+
+## Subagents in any ACP client
+
+A running subagent streams its work onto the parent's tool call as ordinary
+`tool_call_update` content: a bounded log of its tool calls, failures and the
+tail of the message it is writing, with `_meta["graff/subagent"]` naming the
+child. Clients need no changes to show it. `GRAFF_ACP_SUBAGENT_PROGRESS=0`
+turns it off; the draft child-session stream still replaces it when both sides
+opt in.
+
+## ACP v2 preview
+
+Start graff with `GRAFF_ACP_V2=1` and have the client request protocol
+version 2 to get the v2 draft:
+
+- a prompt is acknowledged with the user message's `messageId` as soon as it
+ is inserted, and the outcome arrives as `state_update` (`running`,
+ `requires_action`, then `idle` with a stop reason);
+- every chunk carries a `messageId`, and tool rows are created by
+ `tool_call_update`;
+- `usage_update`, `session/close` and `session/resume` are available.
+
+Every other connection keeps v1 byte-for-byte. See
+[ACP compatibility](../acp-compatibility.md) for what v2 does not cover yet.
+
+## Agents on one device
+
+`graff peer list`, `send`, `inbox` and `read` let any agent on the machine,
+not only graff sessions, list the live agents, post to the current worktree's
+room, and send direct messages.
+
+## Logins across devices
+
+`graff keys` syncs provider logins between your devices through an
+end-to-end encrypted vault. Approve a new device from one you already trust,
+then `push` and `pull` logins, or `put` and `get` single values. Logins that
+rotate their refresh token renew under a vault lease, so two devices never
+race the same refresh.
+
+Kimi requests now identify graff as the platform, and Kimi console keys are
+billed as plan usage.
+
+## Fixes
+
+- An empty JSON-RPC result, such as `session/cancel` with an id, is now `{}`
+ instead of `[]`.
+- Linux builds of `graff peer` compile again.
diff --git a/scripts/eval/tier1-manifest.json b/scripts/eval/tier1-manifest.json
index 26af8314..f6e534be 100644
--- a/scripts/eval/tier1-manifest.json
+++ b/scripts/eval/tier1-manifest.json
@@ -15,7 +15,7 @@
"src/repl.zig",
"TUI/root.zig"
],
- "test_count_baseline": 2823,
+ "test_count_baseline": 2871,
"test_count_slack": 25,
"required_invariants": [
{
diff --git a/src/cli.zig b/src/cli.zig
index 74f1d872..086fbe0e 100644
--- a/src/cli.zig
+++ b/src/cli.zig
@@ -23,6 +23,12 @@ const update_target = @import("update_target.zig");
pub const changelog_text =
\\What's new
\\──────────
+ \\0.0.302.6
+ \\ • ask_user over ACP uses standard elicitation and never freezes a client
+ \\ • ACP subagents stream their work onto the parent tool call
+ \\ • ACP v2 draft preview (GRAFF_ACP_V2=1)
+ \\ • graff peer: message other agents on this device; graff keys: sync logins
+ \\
\\0.0.302.5
\\ • WebSocket turns stream live, with automatic HTTPS fallback
\\ • ACP sessions use the client's folder and report their worktree