graff — a fast agentic coding harness in Zig: multi-provider, MCP, workflows, DGM evolution loop, TS/Python SDKs
v0.0.278 (2026-08-26)
Incremental cut on main after v0.0.277: deleted composer screenshots
must not reach the model (#634).
The bug
On 0.0.276/277 a PNG pasted into the REPL composer and then removed
before submit still rode the pending-image queue. The visible prompt
looked text-only; the first user message still carried native
input_image blocks. Two clipboard pastes could emit four blocks
(each payload twice). The model used the deleted screenshot.
What this cut does
Ctrl-V / drop insert [Image #N] and mark the slot from_composer.
consumePromptImages keeps those payloads only while [Image],
[Image #N], or @[path] is still in the prompt.
/image and /paste are command-staged, so they still ride the next
text-only line. /image clear now clears the whole queue, not just
the last slot. Identical b64 collapses. @[path] restage skips a
path already queued.
TUI chips can leave: backspace on an empty composer drops the last
chip; Ctrl+U / Cmd+Delete clears chips with the draft; overlay
backspace/x detaches the previewed chip. ask_user runs the same
retain-filter before flush.
Bundled Smolify removed
The reserved core Smolify pin (connectSmolify, GRAFF_SMOLIFY /
GRAFF_NO_SMOLIFY, workspace-name lockout, CI boundary E2E) is gone.
CI was already setting GRAFF_NO_SMOLIFY=1 and then asserting the
default catalog advertised Smolify tools — a contradiction that kept
the zig job red.
Add Smolify like any other remote MCP:
graff mcp add smolify --url https://app.smol.ly/mcp
If that name is connected, the local secret-egress gate still refuses
recognizable credentials in mcp__smolify__* arguments. smolify-tools.json
stays as a schema-gate fixture only.
Tests
Unit suite 1683 (floor 1683). The bundled-registration test left with
the server. Tier 1 must stay green without test-smolify-boundary.py.