Release · 2026-09-14T12:41:52Z · By Threadnote

Threadnote 4.7.0

Threadnote 4.7.0 brings current code-linked memory into Claude Code edits and gives every Context Brief client concise action cards.

What's new

Threadnote 4.7.0 brings current code-linked memory into Claude Code edits and gives every Context Brief client concise action cards.

Current memory before Claude edits

threadnote install-hooks claude --apply now installs a selective PreToolUse hook for edits to existing repository files. When Threadnote finds a fresh memory directly cited to the current code, the hook shows its URI and a short constraint before the edit. It stays silent when the citation is stale, the file is unlinked, or the lookup cannot establish a safe match. The agent should read the full memory and verify it against the source.

Action cards in Context Brief

Durable memories can begin with single-line Applies to: and Invariant: fields, plus optional Avoid: and Verify: fields. Context Brief promotes these into a bounded action card only for an exact, current code citation. This works through the CLI and MCP for Codex and other clients as well as Claude; automatic pre-edit delivery is specific to the installed Claude hook. Under a tight brief budget, Threadnote may omit the card while retaining the memory link and coverage evidence, so the full memory remains the source of detail.

More reliable graph and repair operations

Code graph indexing no longer waits behind completed-build cleanup after materialization. When a build is waiting for a database writer or repository lock, graph status shows the verified owning process. threadnote repair --core-only can rebuild Threadnote indexes without changing unrelated agent integrations.

Codex sandbox and local build fixes

The installed CLI can answer threadnote --version inside Codex's workspace-write sandbox without opening a process lease. Commands that need to write the installation root now explain that access requirement instead of exiting silently. Local builds and installs require the repository-pinned Bun 1.4.2 and do not reuse a release built with a different Bun runtime.

Release notes publication

The website's What's New page shows a new stable version only after its GitHub Release is published, even when the release notes file is already on the default branch.