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.17

justrachc2171aabd190
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 98ccdead..743d228c 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -10,6 +10,16 @@ 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.17
+
+### Code mode
+
+- An MCP call inside an rlm script binds the tool's whole result (ADR 0238). Before, a script bound the slimmed cut and could not reach a field it dropped, such as a priority or an estimate; the model had to leave the script and page the stored result back in. `print()` still shows the slim view and now says so, `project(x, field)` reads any field (over an `each()` bind of comment lists, `n` and `latest_author` still read the fold), `write_file` saves the whole result for a script, and inside rlm `read_tool_result("tr_N")` binds a stored result whole. Direct calls are slimmed as before. (#1473)
+
+### Evals
+
+- `evals/graff-vs-pi-codemode`: graff and Pi 1.0, each with its code mode on and off, on harder tasks, with new `mcp-hard` and `aggregate` suites, a Pi 1.0 wrapper (`pi1`, `pi1-codemode`, `pi1-direct`) and an rlm-off arm (`graff-gateway-repl-norlm`). (#1475)
+
## v0.0.302.16
### License
diff --git a/docs/releases/v0.0.302.17.md b/docs/releases/v0.0.302.17.md
new file mode 100644
index 00000000..c6806fb5
--- /dev/null
+++ b/docs/releases/v0.0.302.17.md
@@ -0,0 +1,69 @@
+# Codegraff v0.0.302.17
+
+graff's code mode, `rlm`, now gives a script the whole result of an MCP
+call. Measured against the previous release and against Pi 1.0 with its
+codemode, on two models:
+
+## Evals
+
+### gpt-6-astra: 27% less time on tasks that join MCP data
+
+v0.0.302.16, this release and Pi 1.0 with codemode in its default tools, on
+gpt-6-astra through a ChatGPT plan, interleaved over 11 tasks, 3 runs each:
+
+| | Pass | Wall per task | MCP join tasks | Model calls per task | Input tokens per task |
+| --- | ---: | ---: | ---: | ---: | ---: |
+| v0.0.302.16 | 33/33 | 54.1s | 51.4s | 4.5 | 49.4k |
+| **v0.0.302.17** | 33/33 | **48.3s** | **37.7s** | **3.8** | **44.0k** |
+| Pi 1.0 + codemode | 33/33 | 41.7s | 34.8s | 4.8 | 20.9k |
+
+The join tasks need fields the slim view drops, or a join with local files or
+git history: count issue keys in `src/`, roll issues up by priority, and find
+high-priority issues no recent commit mentions. No run of this release paged a
+stored result back in; 6 of 33 runs of v0.0.302.16 did. Pi with codemode is
+still faster overall and reads less than half graff's input, mostly because
+graff's prompt is larger.
+
+### MiMo v2.6 Pro: the five MCP tasks
+
+The same model, endpoint and key for every arm, interleaved, 3 runs each:
+
+| | Pass | Wall per task | MCP join tasks | MCP report tasks |
+| --- | ---: | ---: | ---: | ---: |
+| v0.0.302.16 | 13/15 | 37.1s | 39.9s | 32.9s |
+| **v0.0.302.17** | 14/15 | **31.0s** | **34.1s** | **26.2s** |
+| v0.0.302.16, rlm off | 15/15 | 38.3s | 51.7s | 18.3s |
+| Pi 1.0 + codemode | 15/15 | 39.3s | 40.6s | 37.4s |
+
+The misses on both graff builds were one report run each that listed the
+issues' display keys instead of their ids. On MiMo rlm still costs time on
+simple fan-out: with rlm off graff answered the report tasks with eight
+parallel calls. Across all 11 tasks v0.0.302.16 took 55.1s per task with rlm
+off against 81.5s with it on, so `--no-rlm` (or `GRAFF_RLM=0`) is worth
+trying on MiMo.
+[Full results](https://github.com/justrach/codegraff/blob/v0.0.302.17/evals/graff-vs-pi-codemode/RESULTS.md).
+
+## rlm scripts keep whole MCP results
+
+graff slims large MCP list results before the model reads them: rows keep
+their id, identifier, title and name, and a comment list becomes a count and
+its latest author. Until this release that applied inside `rlm` scripts too,
+so a script could never reach a field the slim view dropped, such as an
+issue's priority or estimate. The model had to leave the script, call the tool
+directly and page the stored result back in, and the pages' byte-range
+markers broke the JSON when it joined them.
+
+From this release
+([ADR 0238](https://github.com/justrach/codegraff/blob/v0.0.302.17/docs/adr/0238-rlm-binds-keep-the-whole-mcp-result.md)):
+
+- A bind keeps the tool's whole result. It reaches the model only if the
+ script prints it.
+- `print()` still shows the slim view, and now says it is one.
+- `project(x, field)` reads any field. Over an `each()` bind of comment
+ lists, `n` and `latest_author` still read the fold, so existing scripts keep
+ working.
+- `write_file("f.json", x)` saves the whole result for a shell script.
+- Inside a script, `read_tool_result("tr_N")` binds a stored result whole.
+
+A direct MCP call is unchanged: slimmed, with the full result behind a
+handle.
diff --git a/scripts/eval/tier1-manifest.json b/scripts/eval/tier1-manifest.json
index edb8c9b3..ac4c4ba7 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": 3155,
+ "test_count_baseline": 3159,
"test_count_slack": 25,
"required_invariants": [
{
diff --git a/src/cli.zig b/src/cli.zig
index c5e8c65e..2f49c05a 100644
--- a/src/cli.zig
+++ b/src/cli.zig
@@ -23,6 +23,9 @@ const update_target = @import("update_target.zig");
pub const changelog_text =
\\What's new
\\──────────
+ \\0.0.302.17
+ \\ • rlm scripts keep whole MCP results; print() still shows the slim view
+ \\
\\0.0.302.16
\\ • license: companies that raised over US$500k need a commercial license
\\