Release · 2026-08-25T06:53:11+02:00 · By Threadnote

Threadnote 4.3.3

Threadnote 4.3.3 makes code-graph indexing substantially faster and more predictable on large repositories, while fixing cross-process readcontext paging and tightening standalone process cleanup.

What's new

Threadnote 4.3.3 makes code-graph indexing substantially faster and more predictable on large repositories, while fixing cross-process read_context paging and tightening standalone process cleanup.

Faster large-repository graphs

  • Cold graph builds now materialize through a bounded, resumable sorted spool, reducing database write amplification while preserving deterministic graph content and interruption safety.
  • Compiled Tree-sitter queries are reused, parser work is scheduled in wider bounded windows, and large repositories reuse a private validated Git-status cache without changing the repository's real Git index or configuration.
  • Reference-resolution and SQLite work are batched adaptively: ordinary graphs retain conservative transactions while larger reference sets can use wider bounded batches.
  • New stores use 8 KiB SQLite pages, defer cold-only query indexes until the graph is ready, and bulk-build those indexes after materialization.

Proportional incremental indexing

  • Safe body-only edits reuse persisted inventory and load only the changed files' base facts.
  • Export, re-export, and other resolution-surface edits rebuild a bounded dependency-aware project closure instead of automatically replaying the full repository.
  • Additions, deletions, ambiguous attribution, malformed cache evidence, or an oversized dependency closure still fail closed to a complete rebuild.

More reliable agent and installer behavior

  • Concurrent cold graph builds can no longer expose a partially restored query-index schema to another worktree.
  • read_context continuation cursors now persist across MCP processes, remain single-use, expire after ten minutes, and are isolated by tool, scope, account, and user.
  • threadnote graph query --help now states that paging and token budgets require a named Workset and shows the accepted budget range.
  • Development and standalone cleanup now retires stale MCP broker children when superseded Threadnote processes are terminated.

Existing standalone installations upgrade with:

threadnote update