v0.3.8

Highlights

• Clarified the branch feature-memory workflow in installed agent guidance.
• Agents now explicitly recall durable feature memories after branch handoffs before coding.
• Agents now maintain durable feature knowledge separately from handoff state as valuable implementation details, decisions, interfaces, and gotchas emerge.
• README and migration docs now describe the two-record model: durable feature memory for lasting knowledge, active handoff for current status and next steps.

Upgrade Notes

• Run threadnote update to refresh the package.
• Run threadnote install or threadnote repair after updating so user-level agent instructions are refreshed.

v0.3.7

Highlights

• Added lifecycle-aware memory storage that separates current durable knowledge from historical handoff trails.
• Added archive and migrate-lifecycle commands for moving old handoffs into archived lifecycle paths.
• Added packaged post-update migrations so threadnote update can explain and optionally run memory cleanup after upgrading.
• Made migration handling idempotent: reruns reuse existing archived copies and clean up remaining legacy sources.
• Updated user-level agent instructions and README guidance for durable memories, handoffs, replacement, archival, and update migrations.

Upgrade Notes

• threadnote update now runs repair --no-post-update followed by the new package's post-update migration prompt.
• Older updaters that only run repair will still surface applicable post-update migration instructions.
• Use threadnote update --yes for unattended local migrations, or threadnote update --no-post-update to skip them.

threadnote v0.3.6

What's Changed

• Added --replace <uri> to threadnote remember and threadnote handoff so active issue state can be updated without accumulating duplicate progress memories.
• Added replaceUri support to the MCP remember_context tool; the old memory is forgotten only after the replacement memory is stored successfully.
• Added supersedes: metadata to replacement memories and handoffs for auditability.
• Updated the README and installed agent instructions to recommend one current-state memory per active issue, and documented the role split between Threadnote and CLAUDE.md/AGENTS.md.

threadnote v0.3.5

What's Changed

• Fresh installs now start and health-check OpenViking by default, so setup fails early with a log pointer instead of leaving users to hit MCP ECONNREFUSED 127.0.0.1:1933 later.
• Added threadnote install --no-start for CI/manual setup flows that should not start the local server.
• Changed the default Python installer preference to uv, then pipx, then pip, so fresh installs use uv --native-tls and pip-system-certs when available.
• Kept MCP registration explicit while updating README, migration, troubleshooting, and installer next-step docs for the new install flow.

threadnote v0.3.4

What's Changed

• Adds memory compaction guidance to the installed agent instructions: when recall/read surfaces duplicate memories, agents should preserve the important facts and source viking:// URIs in one concise replacement memory, then forget only clearly redundant originals.
• Documents the safety boundary for compaction: do not compact secrets, credentials, customer data, raw production logs, or checked-in canonical docs into memory.
• Updates the README real-world use cases for compaction after long context windows, skill discovery via seed-skills, Cursor support, worktree seeding guidance, and the troubleshooting link in the install flow.

threadnote v0.3.3

What's changed

• Add threadnote migrate-memories to migrate legacy session-only MEMORY and HANDOFF records into durable memory files.
• Support safe dry-runs, per-account selection, all-account scanning, migration limits, duplicate detection, and lightweight sensitive-pattern skips.
• Make migration writes idempotent using deterministic content-hash URIs.

threadnote v0.3.2

What's changed

• Add threadnote update to update the published package and then run threadnote repair so shims and MCP configs point at the new install.
• Add cached npm update notifications for human-facing commands: doctor, start, install, and repair.
• Support npm, Bun, and Deno update paths with --runtime npm|bun|deno|auto.
• Document the update workflow and update-related environment variables.

threadnote v0.3.1

Patch release focused on maintainability and Cursor MCP reliability.

• Move TypeScript sources into src/ and split the large CLI into semantic modules.
• Add ESLint, Prettier, and Husky precommit checks.
• Add Cursor-friendlier MCP tools: recall_context, read_context, list_context, and remember_context.
• Keep compatibility aliases for older MCP flows: search, read, list, and store.
• Return clear Threadnote errors with examples when Cursor calls MCP tools without required JSON arguments.
• Update Cursor agent instructions, README, and troubleshooting docs for the new MCP tool names.

threadnote v0.3.0

Feature release adding first-class Cursor support.\n\n- Add cursor as a supported mcp-install target.\n- Write Threadnote MCP config directly into the global ~/.cursor/mcp.json file while preserving existing Cursor servers.\n- Add Cursor user-rule generation at ~/.cursor/rules/threadnote.md during install.\n- Include Cursor in repair/uninstall MCP handling and installer next steps.\n- Remove the old demo doc from the published package.

threadnote v0.2.2

Patch release for OpenViking repair on corporate networks.\n\n- Avoid refetching the full OpenViking tool when only the Python certificate bridge is missing.\n- Install pip-system-certs directly into the existing OpenViking Python environment via uv pip install --python.\n- Document the direct repair workaround for older Threadnote versions that fail while fetching dependencies such as openai.