Release · 2026-09-22T13:05:24Z · By Threadnote
Threadnote 5.0.0
Threadnote 5 makes engineering context a trustworthy lifecycle: agents begin with a source-aware brief, work from current code, and leave reviewable lessons for the next task.
What's new
Threadnote 5 makes engineering context a trustworthy lifecycle: agents begin with a source-aware brief, work from current code, and leave reviewable lessons for the next task.
An agent can be productive without carrying a whole chat history forward. It still needs the decisions that matter, the state of unfinished work, and a clear way to show what it learned. Threadnote 5 connects those moments without making old memory more authoritative than the repository—or silently turning an agent’s suggestion into team policy.
Set up one supported coding agent in a repository and work normally. Its installed Threadnote guidance automatically starts meaningful work with a focused Context Brief and prepares closeout when it is useful. You remain in control of what is kept, changed, shared, or retired.
Start with context you can trust
A Context Brief is a short, cited starting packet for a task. It brings together relevant reviewed decisions, unfinished work, compatible verified procedures, and evidence from the current code. It also makes uncertainty clear: an unavailable graph, old citation, or incomplete scope is a gap to investigate, not a confident answer.
After setup, you do not need to ask for a brief in every prompt. Give the agent a normal engineering task. The repository and current worktree remain the authority; Threadnote supplies the useful history and source connections around them.
Setup is now a guided, resumable first experience. It connects the selected agent, prepares the repository, checks the installation, and proves the connection with a real brief. It previews changes before applying them and never shares your work merely because setup ran.
Make large monorepos practical
Teams rarely need an index of every package in a large monorepo. A graph scope lets a project select its app or library roots and the declared dependencies they need. Unrelated applications stay outside that project graph, so their changes do not constantly make it stale or consume indexing work.
Preview the scope before using it. Threadnote explains the selected components, files, and diagnostics, and graph answers say when a path is outside the selected boundary rather than claiming it is missing. Scopes follow compatible linked worktrees while keeping dirty worktree evidence isolated. Overlapping scopes can reuse compatible work, and a project without a scope continues to use the full repository graph.
Use a Workset for a different job: it is an intentional group of projects or repositories for a bounded cross-project task. A workset composes prepared graphs; it does not replace a monorepo scope or quietly rebuild code.
Turn closeout into reviewed knowledge
At meaningful closeout, an agent records a private handoff for the next person working on the task. When the work produces a reusable lesson, it also prepares a Knowledge Delta: a small, editable proposal for improving future context.
A Knowledge Delta can capture:
- decisions and their rationale;
- constraints future work must preserve;
- checks that were actually performed;
- knowledge the change made obsolete; and
- risks or questions that remain open.
Review each proposed item, then approve, edit, defer, or reject it. A delta is not an automatic memory write, and approving private knowledge does not publish it to a team. When a decision should be shared, use the normal reviewed Git workflow—including a proposal for teams that use branch review or CODEOWNERS.
Keep approved context useful
Threadnote 5 gives durable context a maintenance lifecycle. Optional ownership, review dates, and expiry dates help identify which decisions need attention without changing what those decisions mean. Existing memory remains readable; the format update adds no invented owner, date, or authority.
Context health checks can surface changed or missing code citations, overdue or expired records, conflicting or duplicated guidance, and broken connections between related memories. Threadnote proposes repair, replacement, or retirement for review. It never silently deletes, rewrites, renews, or chooses a side of a contradiction.
The same evidence can be checked alongside a code change, so a team can see which saved decisions or documentation may need attention before a change is accepted.
Reuse guidance and procedures safely
Existing repository instructions can enter the lifecycle as a reviewable import rather than becoming trusted memory on contact. Once approved, selected knowledge can be projected into supported agents’ native project guidance without overwriting the project-owned text. One reviewed decision can therefore serve several agent environments while the repository’s own guidance remains authoritative.
Threadnote also treats verified procedures as first-class context. A procedure is a reviewed, versioned workflow with compatibility and verification evidence—not something Threadnote downloads and runs on its own. Only procedures that are relevant, compatible, current, and verified can accompany a Context Brief.
Related memories can now be connected explicitly, helping a later reader move from a decision to its constraints, replacement, or supporting record without turning every recall into an unbounded bundle.
See whether context helps
Mark recalled context useful, wrong, pinned, dismissed, or applied when it genuinely informed a plan or change. Threadnote turns those local signals into a private value report covering reuse, closeout outcomes, and health work. It contains counts rather than source code, memory text, queries, paths, repository names, or raw logs, and it is never uploaded by default.
Threadnote 5 is one coherent loop: connect an agent once, let it begin with a focused brief, review the useful lessons it proposes, reuse only what you approved, and keep that context connected to the code as the project evolves.