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.9: shared-broker initialize fix (#1380), desktop apps removed (#1381)

justrach2bce09a28c1f
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 4423b687..f7e2a36b 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -17,11 +17,12 @@ This is the first published release since v0.0.302.6. v0.0.302.7 and v0.0.302.8
### Release artifacts
- The macOS CLI tarballs are Developer ID signed and notarized in the release workflow before upload, so `SHA256SUMS` covers the final files. (ADR 0210)
+- No desktop packages are built here any more. The desktop app is [Harness](https://github.com/justrach/harness), which drives graff over ACP; the in-repo Tauri and Electron apps and the Sidecar Chrome extension are removed. `apps/chrome-native-extension` stays.
### MCP
- Local (stdio) MCP servers start on first use. When a server's tool list is already cached, a session advertises those tools and spawns the process only when a tool is called, so a chat with many configured servers no longer runs them all. A server with no cached list still starts at once to learn its tools. `"startup": "eager"` on an entry, or `GRAFF_MCP_EAGER=1`, keeps the old behavior.
-- `"shared": true` on a stateless stdio server runs one process per machine, shared by every session through a local broker (not on Windows).
+- `"shared": true` on a stateless stdio server runs one process per machine, shared by every session through a local broker (not on Windows). Sessions that attach at the same moment share one `initialize`: a second one waits for the first answer instead of reaching the server again.
- The `tools/list` cache is written under a lock. Servers connecting at the same time could overwrite each other's entries, so a server could look uncached and start eagerly every session.
- `graff mcp add … --everywhere` (alias `--global`) saves to the user-level `~/.codegraff/mcp.json`, which every workspace already merges, so one add applies to every project and to Harness. The verify step, the "saved to" message and live join follow the file that was written.
- ADR 0211 records how MCP servers are named, scoped and synced: a bare name resolves from the codegraff.com catalog and then the MCP registry (only for a matching namespace owner), and cross-device sync carries non-secret rows through Harness while env values, headers and OAuth tokens stay on each device.
diff --git a/src/cli.zig b/src/cli.zig
index d298b1bb..a50778db 100644
--- a/src/cli.zig
+++ b/src/cli.zig
@@ -26,6 +26,7 @@ pub const changelog_text =
\\0.0.302.9
\\ • macOS CLI signed and notarized by the release workflow
\\ • local MCP servers start on first use; "shared": true runs one per machine
+ \\ • the desktop app is Harness; the in-repo desktop apps are removed
\\ • graff mcp add --everywhere saves to the user-level MCP config
\\ • Harness room messages from other agents arrive framed as advisory
\\