Release · 2026-08-27T18:36:45+02:00 · By Threadnote

Threadnote 4.4.1

Threadnote 4.4.1 is a reliability and performance patch for the 4.4 memory-to-code citation release. It keeps legacy uncited memory recall unchanged while hardening graph lifecycle cleanup, isolated graph work, and concurrent logging.

What's new

Threadnote 4.4.1 is a reliability and performance patch for the 4.4 memory-to-code citation release. It keeps legacy uncited memory recall unchanged while hardening graph lifecycle cleanup, isolated graph work, and concurrent logging.

Keep graph work bounded and the Manager responsive

  • Manager-launched graph indexing and Workset preparation run in isolated workers, preserving the Manager service process while concurrent builds report progress independently.
  • MCP impact queries now run behind a hard operating-system timeout with bounded output and child-process cleanup, so a stuck native query cannot hold the MCP server indefinitely.
  • Incremental TypeScript project closure validates dependencies within the changed resolver domain. Unrelated ambiguous package domains no longer force a full rebuild; incomplete or over-bound relevant closure still falls back safely to one full rebuild.
  • Exact-symbol paging and impact-selector resolution preserve precise results at bounded query limits.

Reclaim stale graph state safely

  • Maintenance now reconciles pending view removals, recovers missing or damaged reconciliation cursors, and removes orphaned provenance sidecars and snapshots left behind by deleted worktrees.
  • Cleanup remains lease-aware and fail-closed: active or protected graph generations are not reclaimed, and partial evidence is retried instead of guessed away.

Improve cross-platform reliability

  • Windows production logging retries the narrow, transient sharing failures caused by rapid lock-file replacement. Generic lock callers remain fail-fast, and persistent failures remain bounded.
  • Closed output pipes no longer crash successful CLI work, reused option names are disambiguated, and Bun child-build failures retain their original diagnostics.
  • PDF extraction, telemetry gRPC, YAML tooling, and CI actions receive reviewed dependency updates.

Polish the 4.4 website guidance

  • The home page, Pro Tips, and FAQ explain memory-to-code citations, stale-link warnings, legacy-memory compatibility, and when a Workset is useful.
  • Pro Tips now stays within narrow mobile viewports, including long workflow titles and the horizontal filter strip.

Existing standalone installations upgrade with:

threadnote update

Existing v1, v2, v3, and unversioned memories remain recallable. A Workset is not required for local repository recall or code-graph use; it is an explicit prepared scope for cross-repository queries.