Release · 2026-09-28T17:00:42Z · By Threadnote

Threadnote 5.0.4

Threadnote 5.0.4 keeps CLI and MCP graph analysis responsive while it reports exactly how fresh the selected evidence is, helping agents recover predictably when indexing is busy or storage is constrained.

What's new

Bounded analysis and actionable recovery

CLI analysis, reports, and MCP analysis now use an isolated worker with one end-to-end deadline. When indexing is busy, callers receive bounded recovery information instead of waiting behind it. Persisted summaries and paged fallback remain available without a foreground summary write.

Choose the freshness your task needs

MCP graph analysis now accepts freshness: current, ready, or allow-stale; current remains the default and requires a current snapshot. ready may use compatible existing evidence, while allow-stale never starts indexing. Responses retain the selected policy, snapshot, and scope metadata.

Safer refresh and capacity handling

Equivalent selected project and worktree scopes share refresh demand while sibling projects remain isolated. Whole-build disk estimates stay advisory, while measured per-write reservations remain enforced and retain capacity evidence for later recovery.

Faster indexing in large workspaces

TypeScript graph builds avoid redundant lookups across unrelated dependency packages. Reusing an already-ready graph performs bounded cleanup instead of waiting for all retired graph data, while new builds still reclaim obsolete data before adding another graph. Required cleanup adapts its batch sizes within the existing storage limits.

Lower broker memory use

MCP connection brokers use less memory while retaining automatic updates, session handling, and idle retirement. This reduces the overhead of open agent connections.