graff — a fast agentic coding harness in Zig: multi-provider, MCP, workflows, DGM evolution loop, TS/Python SDKs
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
messageIdas soon as it is inserted, and the outcome arrives asstate_update(running,requires_action, thenidlewith a stop reason); - every chunk carries a
messageId, and tool rows are created bytool_call_update; usage_update,session/closeandsession/resumeare available.
Every other connection keeps v1 byte-for-byte. See ACP compatibility 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/cancelwith an id, is now{}instead of[]. - Linux builds of
graff peercompile again.