Repository navigation
joinweave 0.1.2 — receipt regression; use 0.1.1
Release withdrawn from recommendation — 2026-10-12. A fresh native-service installation with the full MCP dependency inventory exposed an ownership receipt larger than the native 64 KiB safety limit. The node can start, but installer service verification fails. Use the previously verified
npx joinweave@0.1.1while the corrective patch is qualified. Preserve your existing identity and data; do not delete~/.weaveto recover. The attached 0.1.2 artifacts and original validation statement are retained below for traceability.
joinweave 0.1.2 installs a complete developer workspace with a moving ASCII weave, a native Weave node and agent tooling that stays installed locally.
npx joinweave- Installs the native CLI, preserves or creates a local identity, starts a background node and prepares
~/Weave. - Keeps MCP 0.1.0 and its dependencies under
~/.weave/tools/mcp-0.1.0; selected clients use the recorded absolute Node path instead of downloading the server at startup. - Shell PATH and agent-client edits are explicit choices.
--yes --jsonstays machine-readable;--no-animationselects plain progress;--no-mcpskips agent-tool installation and configuration. - Cancellation waits for child termination before cleanup. Retained-data uninstall preserves identity, data and modified or unrelated files.
The native CLI and six scoped packages remain at 0.1.0. Node.js 20+ is required. macOS and supported Linux arm64/x64 are supported; see the installation guide for Linux prerequisites. This npm package does not install Weave Desktop, dBrowser or Loom. The visible workspace folder is not automatically shared.
The exact attached installer archive passed 55 Depot checks, including a real managed MCP install and stdio tool discovery, and is bound to verified Sigstore provenance. Prior live network evidence and the new installer’s validation scope are distinguished in the documentation.