joinweave 0.1.2

Withdrawn from recommended installs

Version 0.1.2 was published on October 12, 2026, then withdrawn from recommended installs after a fresh managed install exposed an ownership receipt larger than the native reader's 64 KiB limit. The embedded MCP file census caused native service ownership checks to fail. Do not select 0.1.2 for a new installation or repair.

Keep existing identity and data. The published 0.1.3 repair moves the census to a hash-bound private file and migrates recognized 0.1.2 receipts before native commands. Its fresh Linux registry flow passed real service/MCP acceptance. Do not purge data to work around this regression.

The history below describes 0.1.2's terminal and persistent MCP changes, not a current installation recommendation. Its native CLI and MCP server were pinned to 0.1.0. The exact 72-frame renderer export remains valid visual evidence, but it does not establish fresh native-install acceptance.

Shell PATH and agent-client configuration remain explicit choices. An unattended --yes --json install includes the MCP server but does not edit client settings. Use --mcp-client codex,cursor to select clients, or --no-mcp to skip the MCP installation and configuration entirely.

Agent tooling stays installed

The server lives at ~/.weave/tools/mcp-0.1.0/node_modules/@useweave/mcp/bin/weave-mcp.js. Configured clients invoke it using an absolute Node executable path and the installed native binary. They do not need to download the server each time they start.

The installer added pinned package-integrity checks, registry-only dependencies, disabled lifecycle scripts and an installed-tree census. That census was embedded in the ownership receipt; the resulting size regression could block native operations and retained-data uninstall. The 0.1.3 installer separates the census before those operations. Modified files and unrelated client entries remain subject to preservation checks.

The client migration code recognized unchanged installer-owned npx entries and updated recorded Node paths on explicit selection. Affected 0.1.2 workspaces still need the compact-receipt repair before native service operations; do not treat the earlier intended rerun/removal behavior as verified acceptance for this version.

Terminal controls

• --no-animation selects plain progress.
• JSON and non-TTY output never animate.
• NO_COLOR disables color; a dumb terminal gets plain progress.
• The animation pauses for prompts and restores the cursor when the installer finishes or is interrupted.
• The visual weave is illustrative. Stage labels and the final component summary report actual installer work.

Cancellation and timeouts stop the active child process before releasing its staging directory. If termination cannot be confirmed, the installer preserves its lock and staging files rather than allowing a second installer to race with that process.

Versions and boundaries

Installation and support covers OS requirements, consent and uninstall. Runtime MCP documents all ten tools and manual setup. The native runtime behavior and prior live-network evidence are documented in the 0.1.1 release.

Weave Desktop is a separate native application. This npm installer does not install a desktop app, a browser, Loom or a public Rust SDK. The visible ~/Weave folder is not automatically shared. Local identity creation does not register an OpenAgentID account.

Read the public package source or view the npm package.