Release · 2026-09-14T20:19:29Z · By Threadnote

Threadnote 4.7.1

Threadnote 4.7.1 keeps exact code evidence and verified memory links clear under tight budgets, and makes sharing and reconnects safer.

What's new

Threadnote 4.7.1 keeps exact code evidence and verified memory links clear under tight budgets, and makes sharing and reconnects safer.

Clearer evidence under small response budgets

Context Brief now protects an exact code card and a relevant linked memory from being crowded out by stale handoffs when the budget permits both. If the card still cannot fit, its follow-up points to the exact graph node. Seeded recall no longer calls a verified connection irrelevant merely because the response budget omitted it; it reports the budget limit and gives a concrete retry size.

More trustworthy graph paths

inspect_code_graph and threadnote graph path check for a direct relationship between the requested endpoints before bounded traversal. When no path fits the search limits, the response says which limits were reached. This search coverage is separate from whether the returned output was truncated.

Safer sharing and reconnects

Share previews and publication accept active personal durable memories only. Previews also warn when a relation target will not be available to the selected team. If an installed MCP runtime exits during a write, Threadnote now reports that the outcome is unknown and asks the agent to read the record before retrying. Manager shows when it is disconnected, preserves unsaved drafts, and asks the user to reconcile a draft if the stored record changed.