Release · 2026-08-28T00:56:51+02:00 · By Threadnote

Threadnote 4.4.2

Threadnote 4.4.2 is a post-release reliability patch for 4.4. It improves Manager graph operations, bounded impact queries, update checks, and runtime diagnostics without changing memory formats or recall behavior.

What's new

Threadnote 4.4.2 is a post-release reliability patch for 4.4. It improves Manager graph operations, bounded impact queries, update checks, and runtime diagnostics without changing memory formats or recall behavior.

Start and refresh graphs directly from Manager

  • Graph Status now lists configured manifest projects before they have a graph snapshot, so a first index can be started without leaving Manager.
  • Project indexing still runs in an isolated process. Actions are fenced to the exact manifest revision, the server-reread project path, and the resolved repository identity. Foreign, missing, or changed entries fail safely, and symlinked paths are canonicalized before readiness and identity checks.
  • Manager distinguishes ready graphs, projects that need initialization, and projects whose readiness is unknown because the bounded catalog was truncated.

Keep active work visible and diagnostics dependable

  • Active graph and Workset operations appear ahead of idle services and legacy runtimes in Manager, including when the process inventory reaches its 100-row bound. Ordinary CLI process diagnostics retain chronological ordering.
  • Doctor tolerates the narrow registration window while a live process atomically publishes its diagnostic record.
  • Extracted standalone release checks use their bundled version instead of inheriting an unrelated development installation's version.

Keep bounded graph reads bounded

  • Isolated MCP impact reads no longer spend their fixed 20-second budget starting a base-commit graph build. They reuse a ready current-format base snapshot when available; otherwise they return current evidence with an explicit warning that deleted-path recovery was skipped.
  • Slow vector benchmark failures retain their evidence artifact, and Windows release-metadata probes keep their substantive verification while allowing for load-sensitive archive startup.

Existing standalone installations upgrade with:

threadnote update

Existing v1, v2, v3, and unversioned memories remain recallable. A Workset is still optional for local repository recall and graph use.