Release · 2026-09-02T07:32:53+02:00 · By Threadnote

Threadnote 4.6.1

Threadnote 4.6.1 makes Personal Cursor Cloud a supported one-person setup: one MCP can span up to 16 private Git memory shares and bootstrap Cursor 4.6 Agent Skills into every saved cloud environment.

What's new

Use one personal MCP across multiple memory shares

Personal Cursor Cloud no longer treats one Git memory repository as the whole environment. Bootstrap each private repository as a named share, then generate one MCP configuration with the same repeated team set:

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

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

threadnote cloud cursor config \
  --team personal \
  --team docs \
  --user cursor-cloud \
  --agent-id cursor-cloud

Paste the generated stdio configuration into one personal MCP server named threadnote in the Cursor Cloud Agents dashboard. Team ordering and duplicates are normalized, and the generated configuration uses the stable cursor-cloud-personal toolset. Existing cursor-cloud and cursor-cloud-git-beta identifiers remain accepted as compatibility aliases.

The single MCP keeps each share bounded and independently synchronized:

recall_context searches every configured share by default and accepts team to narrow the search.
read_context can open returned URIs from any configured share.
list_context requires team or an exact in-scope uri when more than one share is active.
Durable remember_context writes require an explicit team in a multi-share setup. Commits and pushes stay in that repository, while cross-share replacements, references, and relations fail closed.
Handoffs remain VM-local because Cloud Agent disks are disposable; use a sanitized durable memory when another session must receive it.

Share remotes must be credential-free HTTPS URLs, and the Git identity connected to the personal Cursor environment must have read-write access. A repository not found error means the environment identity cannot see the repository, the URL is wrong, or the repository has not been created; a Threadnote share name does not grant access.

Bootstrap Cursor 4.6 instructions inside the Cloud VM

Cursor does not copy user-level skills from a developer laptop into Cloud Agents. Each personal bootstrap now installs a Cloud-safe always-on rule and three progressively loaded skills under ~/.cursor/skills:

threadnote-context recalls and reads relevant decisions before non-trivial work.
threadnote-code-graph discovers current source relationships before broad text search.
threadnote-memory preserves reusable decisions and closeout handoffs without leaking secrets.

The instructions match the personal boundary: one MCP, multiple explicit Git shares, local-only code graphs, explicit durable-write routing, and VM-local handoffs. threadnote cloud cursor verify now accepts repeated --team flags and returns a version-2 receipt with the complete teams and memoryRoots set.

Do not run threadnote mcp-install cursor --apply inside this environment. That command manages Cursor Desktop. Add the generated personal stdio MCP in the Cloud Agent UI, make the successful environment Build active, and start a fresh agent after changing the runtime, MCP configuration, rule, or skills.

Follow the standalone setup guide

The new Personal Cursor Cloud setup guide covers private repository creation, saved-environment installation, one-MCP registration, multi-share routing, verification, and recovery from missing repository access or mismatched share configuration. Organization-operated remote memory remains a separate deployment model and must not be registered alongside the personal profile in the same environment.

Existing Threadnote 4 installations upgrade after the immutable release is published with:

threadnote update