Release · 2026-11-07T09:23:57Z · By Threadnote

Threadnote 5.3.5

Threadnote 5.3.5 makes local recall and graph work more dependable, with purposeful embedding controls and fewer avoidable waits.

What's new

Threadnote 5.3.5 makes local recall and graph work more dependable, with purposeful embedding controls and fewer avoidable waits.

Recall without avoidable waits

threadnote recall and MCP recall now read a ready local snapshot while automatic synchronization and index maintenance continue in the background. Foreground recall waits for validated data, a real failure, or cancellation from its caller instead of stopping at an internal timeout.

Confirm lexical and vector recall preparation

threadnote repair and threadnote index rebuild now wait for lexical and vector recall indexes to be ready for the inputs they inspected. They report source, model, or authorization drift rather than presenting outdated recall readiness as current.

Choose embedding models by purpose

Optional EmbeddingGemma 2 and Qwen3 Embedding 0.6B models can be selected independently for code graph and memory recall vectors after they are installed and verified. For example, use threadnote models select embeddinggemma-2-q8 graph and threadnote models select qwen3-embedding-0.6b-q8 recall; the existing shared embedding selection remains the fallback when no purpose-specific choice is set.

Let foreground graph preparation finish

When a native workflow prepares its graph, it can now wait for completion, failure, or caller cancellation instead of stopping at an internal timeout.

Keep workset catalogs consistent

Code-graph workset catalog reads now synchronize initialization and migration work so normal requests see a consistent available catalog instead of encountering a readiness race.

See the next workflow task

Use threadnote workflow task-view --run-id <id> --caller-cwd <path> or the workflow_task_view MCP tool to read the next actionable task for an existing native workflow run, with optional implementation, review, or delivery role filtering.

Safer workflow handoffs

Native workflow cycles preserve source evidence when an ordinary merge updates their base. Review follow-ups now keep shared feature knowledge current without duplicate publication requests, so task and review history stays connected to the source that actually shipped.

Clearer Manager availability

Manager now explains when a ready recall snapshot is temporarily unavailable and directs you to retry after background maintenance or run threadnote repair.

More flexible development plans

Development plans can describe an architecture clearly in prose when a diagram would not add useful understanding.