Release · 2026-08-12T14:39:20+02:00 · By Threadnote

Threadnote 4.2.0

Threadnote 4.2 brings multi-repository Projects and Worksets into Manager, extends native graph investigation across prepared repository sets, and makes graph storage and local runtime activity easier to understand and control. It also introduces an initial Cursor Cloud Agents shared-memory profile and safer stable and preview updates.

What's new

Threadnote 4.2 brings multi-repository Projects and Worksets into Manager, extends native graph investigation across prepared repository sets, and makes graph storage and local runtime activity easier to understand and control. It also introduces an initial Cursor Cloud Agents shared-memory profile and safer stable and preview updates.

Manage Projects and Worksets end to end

  • Manager can create, inspect, edit, rename, and delete manifest Projects and Worksets, including an Add your first project flow for an empty manifest. Project cards lead with the repository folder and observed branch instead of opaque checkout IDs.
  • Project writes preserve supported YAML comments and use revision-fenced atomic updates. Git roots are canonicalized, duplicate checkout ownership is rejected, and seeding blocks escaping patterns, symbolic-link traversal, and path-swap races.
  • Renaming a Project updates referencing Worksets in the same transaction. Deleting one leaves dependent member names visibly unresolved and never deletes repositories, seeded resources, memories, or graph databases.
  • Worksets can prepare a published graph generation, then run bounded queries and continuation, exact paths, reverse impact, topology, and Context Briefs with per-repository provenance. Queries never fan out cold builds; run threadnote workset prepare <name> when a member needs its first or a fresher ready snapshot.
  • Client-injected agent guidance is shorter, graph-first for unfamiliar source, and documents the same published-ready Workset contract.

Keep graph storage and runtimes bounded

  • Retired repository snapshots and Workset generations are reclaimed with bounded storage admission and physically paged cleanup, preventing repeated builds from accumulating retired payloads without bound.
  • Manager distinguishes allocated SQLite pages, useful live data, and reusable freelist space. While Manager is running, it automatically compacts at most one eligible freelist-heavy database at a time after conservative disk-headroom, cooldown, build, and maintenance checks.
  • The Processes tab shows a compact, privacy-safe inventory of registered Threadnote runtimes. Graph compaction and deep-diagnostics workers appear only while alive, and a confirmed identity-bound icon action can stop a selected process without exposing arguments, environment variables, paths, or private registration data. The current Manager is protected.
  • Graph databases with neither a verified folder nor a ready snapshot are labeled unassociated graph storage, with explicit guidance to index from the repository folder or preview and purge obsolete derived data.
  • The core embedding model is available from an immutable Threadnote release asset, with resumable transfer, SHA-256 verification, and atomic promotion when Hugging Face is unavailable.

Update safely across stable and previews

  • Stable installations continue to select stable releases only. The beta channel is inclusive: it selects the newest immutable stable or prerelease, so an invoked update from beta.2 can discover Threadnote 4.2 without --stable. After graduation, ordinary updates infer stable-only selection again; use threadnote update --beta to re-enter preview selection.
  • threadnote update --force refuses semantic downgrades, preventing stale or incomplete release listings from turning a forced reinstall into an older installation. Reinstalling the current version and upgrading remain supported; an explicit threadnote update --stable can still move a prerelease to an older stable release.
  • Release archive checksum verification, installation locking, and atomic promotion remain in force.

Try the Cursor Cloud Agents profile (beta)

  • The initial Cursor Cloud profile adds threadnote cloud cursor config, bootstrap, and verify commands for deterministic stdio MCP setup, idempotent writable-share preparation, and runtime verification in an ephemeral checkout.
  • The profile confines memory reads and durable writes to one designated Git-backed share. Durable writes are scrubbed, committed, and pushed; local code-graph inspection remains available for the current checkout while Worksets, maintenance, review, and separate publishing tools are disabled.
  • Full first-class Cursor Cloud lifecycle automation is still in development. Keep Git credentials outside repository files, remote URLs, MCP JSON, and agent instructions, and treat VM-local handoffs as transient.

Upgrade to Threadnote 4.2

Existing standalone installations upgrade with:

threadnote update

An installation already following the beta channel also discovers stable 4.2 automatically because it is newer than the 4.2 prereleases. For a fresh macOS or Linux installation:

curl -fsSL https://raw.githubusercontent.com/Kashkovsky/threadnote/main/scripts/install.sh | sh

Updates preserve Threadnote data and verified model files.