Skip to main content

Version Selection

Use this page to choose a LocalNest version line and install it explicitly.

  • Want the current stable release: use 0.0.5
  • Want the previous stable behavior: use 0.0.3
  • Need older behavior for compatibility: use the archived beta rows below

Common upgrade commands:

localnest upgrade stable
localnest upgrade beta
localnest upgrade 0.0.5
localnest upgrade 0.0.3

Install commands by version

VersionChannelInstall command
0.0.5current stablenpm install -g localnest-mcp@0.0.5
0.0.4-beta.9archived betanpm install -g localnest-mcp@0.0.4-beta.9
0.0.4-beta.8archived betanpm install -g localnest-mcp@0.0.4-beta.8
0.0.4-beta.7archived betanpm install -g localnest-mcp@0.0.4-beta.7
0.0.4-beta.6archived betanpm install -g localnest-mcp@0.0.4-beta.6
0.0.4-beta.5archived betanpm install -g localnest-mcp@0.0.4-beta.5
0.0.4-beta.4archived betanpm install -g localnest-mcp@0.0.4-beta.4
0.0.3stablenpm install -g localnest-mcp@0.0.3
0.0.2-beta.3archived betanpm install -g localnest-mcp@0.0.2-beta.3
0.0.2-beta.2archived betanpm install -g localnest-mcp@0.0.2-beta.2
0.0.1-beta.1archived betanpm install -g localnest-mcp@0.0.1-beta.1

Post-install command differences

Versionlocalnest-mcp-install-skillSetup style
0.0.5yesstable promotion of beta.9 fixes + installed-runtime validation hardening
0.0.4-beta.9yesskill version reporting fix + beta.8 runtime baseline
0.0.4-beta.8yesstartup/runtime regression fixes + sqlite-vec status hardening
0.0.4-beta.7yesglobal-first + sqlite-vec auto-detection + Hugging Face runtime
0.0.4-beta.6yesglobal-first + release-hardening + restructured internals
0.0.4-beta.5yesglobal-first + localnest upgrade command path
0.0.4-beta.4yesglobal-first + memory consent
0.0.3yesglobal-first
0.0.2-beta.3yestransitional (npm -g + npx setup common)
0.0.2-beta.2yes (introduced here)transitional
0.0.1-beta.1nonpx-first setup flow

Notes

  • If you need deterministic behavior across environments, pin exact versions instead of using floating tags.
  • The phrase "beta 9" in this repo maps to 0.0.4-beta.9 package naming.
  • Use Release Matrix for context, Current Release for active stable behavior, and the archived per-version pages for 0.0.4-beta.9 or 0.0.4-beta.8 when you need frozen prerelease notes.