joinweave 0.2.0
Runtime API 2, 46 MCP tools, six persistent models and a consented upgrade path.
Release status
Published and registry verified. All seven npm packages are published at 0.2.0, and their latest tags select 0.2.0. Exact archive, integrity, provenance and version verification completed on October 12, 2026 at 8:18:26 PM CT. Separate fresh-install and 0.1.3 upgrade flows passed against the actual npm registry on October 13, 2026 at 12:32 AM CT.
| Release check | Verified result |
|---|---|
| Seven exact npm archives, provenance and version metadata | Passed in Depot 3dnwbjqwqz, October 12 at 8:18:26 PM CT |
npm latest selects 0.2.0 | Verified for joinweave and all six companion packages |
| Fresh registry installation on a new Linux x64 systemd user | Run 38351874053, job 115145869420: eight checks passed; completed October 13 at 12:32:25 AM CT |
| Real registry upgrade from 0.1.3 with retained identity/data and old MCP clients | Run 38351874053, job 115145869060: twelve check records passed; completed October 13 at 12:32:32 AM CT |
Both registry jobs returned successful operator exits and completed owned-account cleanup. The publication receipt is bound by SHA-256 5aa71a3c80bdf4109f902bf395d7af776ac57c91f077c98fea5e5d5ae912836e. Public joinweave metadata and its npm attestation identify the published package. Older release evidence remains specific to its own archives and installed flows.
Matching components
| Package | Version | Role |
|---|---|---|
joinweave | 0.2.0 | Workspace installer and managed upgrade |
@useweave/cli | 0.2.0 | Launcher with exact native optional dependencies |
@useweave/mcp | 0.2.0 | 46 typed tools over local stdio |
@useweave/cli-darwin-arm64, @useweave/cli-darwin-x64 | 0.2.0 | macOS native packages |
@useweave/cli-linux-arm64, @useweave/cli-linux-x64 | 0.2.0 | Linux native packages |
The native executable and service ownership-receipt protocol remain 0.1.0. The runtime capability contract is API 2. weave --version cannot distinguish the old runtime from this update; use weave capabilities --json.
The frozen package manifest identifies all seven exact archives. Public packaging source contains Node tooling and prebuilt executables; the native Rust implementation remains private. A manifest is an input binding, not proof of publication or a completed registry installation.
A persistent developer workbench
The MCP combines 17 core tools, one capability-discovery tool and 28 model tools:
| Model | Operations | Contract |
|---|---|---|
| Locus | 7 | Virtual drives, directories, file bytes and metadata |
| Lens | 6 | Key/value writes, reads, deletion, ranges and listings |
| Forum | 4 | Exact-byte tuple writes, reads and consuming takes |
| Gnosis | 4 | Graph creation, triples, queries and neighbors |
| Basis | 4 | UUID-addressed vectors and similarity search |
| Nexus | 3 | Timestamp-ordered views combining named Strands |
The MCP guide lists all 46 tools, their inputs and limits. Model operations use the persistent node; reads do not create missing stores. Locus paths are virtual paths, not arbitrary host filesystem access. Models do not mount, mirror or automatically publish data. Announcing and seeding do not encrypt plaintext Strands.
Install and upgrade
Install the verified version:
npx joinweave@0.2.0Platform requirements remain Node.js 20+, macOS arm64/x64 or Linux arm64/x64 with the documented native libraries. No user-side Rust compilation is required.
An upgrade verifies ownership, stops the old owned node before replacing its binary and restarts with the same identity and data. A durable old/new hash-bound journal supports interrupted replacement recovery through reinstall or retained-data uninstall. Foreign or modified bytes are refused rather than overwritten.
The installer adds ~/.weave/tools/mcp-0.2.0 while retaining the old 0.1.0 tree and census for clients that still reference them. Headless installation leaves client files unchanged and reports mcpClientsNeedingUpdate. To migrate only selected intact owned entries:
npx joinweave@0.2.0 --yes --mcp-client codex,cursor --jsonRestart those clients. Unrelated or modified entries are preserved. Uninstall removes unchanged owned integration while retaining identity and data; modified or still-referenced tool trees remain. --purge is explicit and destructive. The recognized 0.1.2 compact-receipt repair remains supported.
Evidence boundaries
Native archive qualification and unit checks are separate from real installed acceptance. The two successful jobs in run 38351874053 each used a new Linux x64 user, a genuine systemd session, an empty unseeded npm cache and canonical registry downloads. They verified installed archive integrity, default native resolution without WEAVE_BINARY, 46-tool discovery, matching MCP/native/service PID, restart, owned-service crash recovery and retained-data uninstall.
The upgrade job installed the real 0.1.3 predecessor before upgrading to 0.2.0. It preserved identity and data, retained the old MCP tree and unchanged client settings, exercised explicit client migration, and verified all six model families across restart, including deletion/consumption behavior. The fresh flow recorded eight checks and the upgrade flow twelve; these are acceptance records, not counts of individual assertions.
The fresh result receipt has SHA-256 62b9430f5f8f0095aac83d3992cf7cf52bf474c1efc88cb56bea8c22ed67bd66; the upgrade receipt has SHA-256 220f2a7cef0efc5ef5dd23ac362763495223a3d972b699f0c84e1a4abc827a0f. Their exact completion times were 2026-10-13T05:32:25.498Z and 2026-10-13T05:32:32.875Z, respectively. Both operator receipts report exit 0 and successful cleanup.
These Linux x64 flows do not establish the same managed-install behavior on macOS or ARM64. Preserve platform qualification separately and report its actual scope. The 0.1.1 and 0.1.3 records remain evidence for their own versions.
Separate work
The installer does not install Weave Desktop. Desktop and its selected-file MCP bridge remain development work; public Apple-signed distribution is on hold. Workspace MCP has local CLI authority and does not inherit Desktop’s selected-file grants.
Cores storage remains a separate pilot, not a purchased persistence service bundled with joinweave. This release does not issue MINT, register or link OpenAgentID/LifeID accounts, or publish an npm SDK. Official MCP Registry metadata is prepared; a Registry submission and listing are separate from npm publication.
