Release · 2026-08-13T11:31:19+02:00 · By Threadnote

Threadnote 4.2.2

Threadnote 4.2.2 keeps native code graphs available while work moves across linked worktrees and reduces unnecessary whole-repository graph rebuilds after ordinary source-file changes. It also keeps existing MCP transports connected when a standalone update or exact-HEAD development install activates a new runtime.

What's new

Threadnote 4.2.2 keeps native code graphs available while work moves across linked worktrees and reduces unnecessary whole-repository graph rebuilds after ordinary source-file changes. It also keeps existing MCP transports connected when a standalone update or exact-HEAD development install activates a new runtime.

MCP sessions survive runtime promotion

  • MCP launchers now keep a small stable session broker on editor-owned stdio and promote the versioned Threadnote MCP runtime behind it at a request boundary.
  • Requests already admitted to the previous runtime finish there. Threadnote never automatically replays a tool call whose outcome could be unknown.
  • threadnote update and exact-HEAD development installs use the same active-release promotion contract. Sessions started before this release still need one host restart to enter the brokered architecture.

Ready graphs across active worktrees

  • A newly created linked worktree can attach an existing clean snapshot immediately instead of waiting for another cold graph build.
  • After a source edit, graph queries continue to return usable current or stale evidence while the refreshed snapshot converges, across TypeScript, Python, and Rust repositories.
  • Two worktrees from the same repository can build at the same time without sharing dirty state or blocking one another.

Smaller refreshes for project-scoped changes

  • Adding, deleting, or renaming a source file inside a complete declared project graph now refreshes only the affected project and its reverse dependencies when that closure is safe and bounded.
  • The same bounded behavior applies to uncommitted edits and committed changes.
  • Ambiguous ownership, incomplete project metadata, global resolution changes, and other uncertain cases still fall back to full materialization.

To require evidence from the latest graph after an edit, run:

threadnote graph query --cwd /path/to/worktree --freshness current --query YourSymbol

Existing standalone installations upgrade with:

threadnote update