Release · 2026-09-15T09:39:36Z · By Threadnote

Threadnote 4.7.3

Threadnote 4.7.3 reuses ready code graph evidence during long rebuilds, quiets ignored filesystem changes, and gives clearer recovery steps when a read or build cannot finish yet.

What's new

Threadnote 4.7.3 reuses ready code graph evidence during long rebuilds, quiets ignored filesystem changes, and gives clearer recovery steps when a read or build cannot finish yet.

Ready graph evidence during rebuilds

inspect_code_graph query, node, neighbors, and explain requests can use an existing stale ready snapshot without scanning the worktree or waiting for a competing graph builder. Current relationship paths and impact analysis still require fresh worktree evidence.

Quieter filesystem graph watches

Repository watches now apply Git ignore rules, .threadnoteignore, and .threadnoteignore.local before filesystem events trigger maintenance or a refresh. Changes to ignore manifests remain relevant and reload the watch rules, so generated output in ignored directories no longer starts needless graph work.

Clearer waiting and timeout responses

When child build status cannot be read while a database writer is active, graph progress says it is waiting on the writer instead of remaining at registering, and the response asks callers to retry after the writer releases. If reading a ready snapshot itself exceeds the MCP foreground budget, the response reports a read timeout and points to the CLI's explicit ready freshness and longer read timeout instead of suggesting repeated five-second indexing retries.