Release · 2026-08-17T17:32:30+02:00 · By Threadnote

Threadnote 4.2.6

Threadnote 4.2.6 makes code graph indexing resilient to busy worktrees, so ordinary inspections stay fast while explicit current-only operations can safely refresh the graph.

What's new

Threadnote 4.2.6 makes code graph indexing resilient to busy worktrees, so ordinary inspections stay fast while explicit current-only operations can safely refresh the graph.

Stable inspection during active development

  • query, node, neighbors, and explain now serve an existing ready snapshot with stale context instead of starting a repository-wide rebuild. path, impact, analyze_code_graph, and explicit graph index remain current-only.
  • Filesystem and periodic refreshes only resume incremental overlay work after a compatible assessment for the current ready base. Otherwise Threadnote keeps serving the stale snapshot and explains how to request current state.

Reuse finished work when the worktree moves

  • A snapshot that finishes committing before HEAD or the local overlay changes is retained as a reusable base instead of being discarded and rebuilt from scratch.
  • Retirement after interrupted or incomplete builds is page-budgeted, retaining storage backpressure without extending the activation window.

Bounded builders and safer incremental TypeScript edits

  • Repository-sized builders are coalesced per worktree across Threadnote hosts and limited to two concurrent builders per home. Explicit current requests get the next available slot ahead of background refreshes.
  • Private TypeScript declarations whose lookup keys are proven local to their own path stay on the incremental overlay path. Other resolution domains and published-surface changes remain fail-closed.

Existing standalone installations upgrade with:

threadnote update