Release · 2026-11-09T12:57:09Z · By Threadnote

Threadnote 5.3.6

Threadnote 5.3.6 makes native workflows easier to recover and trust, with clearer task actions, safer review recovery, qualification after upstream rewrites, and private read-only memory previews.

What's new

Threadnote 5.3.6 makes native workflows easier to recover and trust, with clearer task actions, safer review recovery, qualification after upstream rewrites, and private read-only memory previews.

Preview private memories locally

Memory launch links now have a private, read-only local preview foundation. Stable memory IDs are resolved with bounded scans that offer an explicit Continue scanning action when more work is needed, and content larger than 512 KiB is rejected before it is read.

General agent-emitted clickable memory links remain disabled until the separate desktop and HTTPS integration work is complete.

Coordinate workflows through task actions

Native workflows now expose task-oriented MCP and CLI actions for authoring, implementation, review, validation, delivery, and closeout. Use threadnote workflow-automation task-view --run-id <id> --caller-cwd <path> or the workflow_task_view MCP tool to read the next action and its guarded task reference instead of assembling workflow revisions and receipts by hand.

Task views verify closeout bodies, commit delivery is available through the task-action CLI, and exact delivery replays return the previously stored result. Provisional pull-request watches can also recover without losing their workflow history.

Recover blocked reviews with explicit authority

When a review-recording task is blocked, threadnote workflow-automation task-action record-review can accept the blocked task reference and a human authority statement:

threadnote workflow-automation task-action record-review --run-id <id> --caller-cwd <path> --snapshot-ref <ref> --task-ref <task-ref> --user-authority "<statement>" --report '<json>'

Each task reference permits one distinct corrected attempt, while an exact replay returns the stored result. Snapshot task cards now show whether lineage recording is required and whether extending the review budget needs approval.

Requalify after upstream base rewrites

Workflow cycles can qualify again after an approved upstream branch rewrite while preserving their original baseline, findings, attempts, and review budget. The rewritten base requires a fresh full review before delivery can continue.

Saving unchanged authoring content now checks the current source witness. Stale approvals and reviews are handled explicitly, rejected starts leave task state unchanged, and source or schema errors identify the business field, bounded relative path, and expected shape that need correction.

Keep shared hashing reliable

Shared graph identity and fingerprint hashing now uses Bun's native SHA-256 implementation while preserving the existing hexadecimal output. This also prevents Manager's Chromium runtime from failing consolidation and review flows when the Bun global is unavailable.