graff — a fast agentic coding harness in Zig: multi-provider, MCP, workflows, DGM evolution loop, TS/Python SDKs
Python
Release v0.302.31
justrach65d811634897
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 5bdaded7..7347be09 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -10,6 +10,18 @@ The release workflow uses a tag's section here as its release notes (ahand-written `docs/releases/<tag>.md` wins if present), so keeping this filecurrent is part of cutting a release.+## v0.302.31++### ACP++- Tool rows for tools whose only end is a finish event (`peer_message`, `load_tool_schemas`, `todo_write`) now get their completed or failed status. They stayed "in progress" in clients such as the desktop app. Ordinary tools still end once, on their result (#1600).++### Updating++- `graff update` works on Windows. It ran `install.sh` through `/bin/sh`, which Windows does not have, and failed with "could not launch installer". It now runs the release's `install.ps1`, which verifies the download and replaces the running `graff.exe`, also when graff runs inside PowerShell 7.+- The Windows installer no longer reports "graff.exe did not start" after a successful install.+- `graff --help` lists `graff login anthropic`.+## v0.302.30Releases are now tagged with three parts (`v0.302.N`). `graff update` treats v0.302.30 as newer than every v0.0.302.N.diff --git a/docs/releases/v0.302.31.md b/docs/releases/v0.302.31.mdnew file mode 100644index 00000000..492cfebd--- /dev/null+++ b/docs/releases/v0.302.31.md@@ -0,0 +1,34 @@+# Codegraff v0.302.31++Tool rows that never finished, and `graff update` on Windows.++## Every tool row finishes++Some tools end without a result on graff's event stream: `peer_message`,+`load_tool_schemas` and `todo_write` only send a finish event. graff's ACP+output ignored that event, so clients such as the desktop app showed those+tools as running forever. Each of them now gets its completed or failed+status. Ordinary tools still end once, on their result.++## `graff update` on Windows++`graff update` ran the shell installer through `/bin/sh`, which Windows does+not have, so it failed with "could not launch installer". On Windows it now+runs the release's `install.ps1` into the folder graff is installed in. The+installer checks the download against the release's SHA256SUMS and replaces+the running `graff.exe`. It works from Command Prompt, Windows PowerShell and+PowerShell 7.++If you are on Windows with an older graff, update once by running the+installer again:++ irm https://github.com/justrach/codegraff/releases/latest/download/install.ps1 | iex++`graff update` works from then on.++## Also++- The Windows installer no longer reports "graff.exe did not start" after a+ successful install. Its version check cut graff's output short, which made+ graff exit with an error.+- `graff --help` lists `graff login anthropic`.diff --git a/scripts/eval/tier1-manifest.json b/scripts/eval/tier1-manifest.jsonindex 68bea22b..c4b5d8d0 100644--- a/scripts/eval/tier1-manifest.json+++ b/scripts/eval/tier1-manifest.json@@ -14,7 +14,7 @@"src/main.zig","src/repl.zig"],- "test_count_baseline": 3223,+ "test_count_baseline": 3228,"test_count_slack": 25,"required_invariants": [{diff --git a/src/cli.zig b/src/cli.zigindex b09d4250..b63958e9 100644--- a/src/cli.zig+++ b/src/cli.zig@@ -24,6 +24,10 @@ const update_target = @import("update_target.zig");pub const changelog_text =\\What's new\\──────────+ \\0.302.31+ \\ • tool rows for todo_write, peer_message and schema loads finish in ACP clients+ \\ • graff update works on Windows+ \\\\0.302.30\\ • graff mcp status / reconnect / enable / disable, and /mcp reconnect in a session\\ • graff login anthropic: use an Anthropic Console account