Release · 2026-09-02T09:13:51+02:00 · By Threadnote

Threadnote 4.6.2

Threadnote 4.6.2 fixes two Personal Cursor Cloud provisioning races discovered in a real multi-share environment.

What's new

Threadnote 4.6.2 fixes two Personal Cursor Cloud provisioning races discovered in a real multi-share environment.

MCP discovery stays available during share bootstrap

The Personal Cursor Cloud MCP server no longer requires every declared Git memory share to be configured read-write before it advertises tools. Cursor can start the MCP process while a saved-environment Build is still cloning several shares, so that boot-time requirement could terminate the server and make the entire threadnote namespace disappear.

The MCP now establishes its bounded share scope from the declared configuration immediately. Memory operations check share readiness when they run and return an actionable temporary warning until bootstrap finishes. The same process can use the shares as soon as they become ready; MCP discovery and local code-graph tools remain available throughout.

Personal identity no longer falls back to the Cloud VM user

Personal bootstrap now atomically saves the selected account, user, and agent identity in ~/.threadnote/cursor-cloud/profile.json before cloning the first share. Later CLI, index, doctor, verify, and MCP processes inherit that profile when explicit environment variables are absent, instead of resolving the generic Cloud Agent OS user such as ubuntu.

Explicit THREADNOTE_* identity variables and command flags still take precedence. Threadnote refuses to silently replace a saved profile with another user in the same home because doing so would strand the existing canonical memory cache. Use the same --user and --agent-id for every share, or use a separate THREADNOTE_HOME for an intentionally separate identity.

To repair an affected environment, update Threadnote and rerun every existing bootstrap command once with the identity that owns the populated canonical memory tree, then regenerate the one personal MCP configuration with those same values. For example:

threadnote update

threadnote cloud cursor bootstrap \
  --remote https://github.com/you/threadnote-memory.git \
  --team personal \
  --user your-stable-threadnote-user \
  --agent-id cursor-cloud

threadnote cloud cursor config \
  --team personal \
  --user your-stable-threadnote-user \
  --agent-id cursor-cloud

Repeat --team in the configuration command and rerun bootstrap once per remote when the MCP exposes multiple shares.