Installation and support
Supported platforms, release versions, consent and workspace ownership.
Current packages
| Package | Current version | Purpose |
|---|---|---|
joinweave | 0.1.1 | Workspace installer and retained-data uninstall |
@useweave/cli | 0.1.0 | Node launcher for the native weave executable |
@useweave/mcp | 0.1.0 | Runtime MCP server over stdio |
@useweave/cli-darwin-arm64, @useweave/cli-darwin-x64 | 0.1.0 | macOS prebuilt executables |
@useweave/cli-linux-arm64, @useweave/cli-linux-x64 | 0.1.0 | Linux prebuilt executables |
The installer patch does not change the native or MCP versions. Version-specific evidence is on the 0.1.1 release page.
Prerequisites
Use Node.js 20 or newer with npm/npx available. Keep optional dependencies enabled so npm can select the native package matching the Node process's OS and architecture.
| Platform | Architecture | Native requirements | Managed background node |
|---|---|---|---|
| macOS | Apple Silicon / arm64 | Executable minimum load target: macOS 11 | User launchd session |
| macOS | Intel / x64 | Executable minimum load target: macOS 11 | User launchd session |
| Linux | x64 | glibc 2.39 or newer | Working systemd --user session |
| Linux | arm64 | glibc 2.39 or newer, libssl.so.3 and libcrypto.so.3 | Working systemd --user session |
Windows, musl distributions and older glibc versions are unsupported by this release. The macOS value is the binary's load target, not a claim that every macOS 11 configuration has been tested. Your chosen Node version must also support your OS.
The node needs network access to public peers, including the default dht1.weave.earth, dht2.weave.earth and dht3.weave.earth bootstrap endpoints on TCP 4001. Public connectivity and relay capacity depend on the network. No account login or private-key upload is part of installation.
Install
npx joinweaveFor a pinned headless install:
npx joinweave@0.1.1 --yes --json--json produces one JSON result on stdout, without prompts. Failure returns ok: false and a nonzero exit status. Doctor failure is installation failure; the recoverable workspace and node may remain for diagnosis and a rerun.
| Option | Behavior |
|---|---|
--yes | Headless install; skips PATH and MCP questions |
--json | One machine-readable result; no prompts |
--path | Explicit consent to add a managed shell PATH entry |
--mcp-client CLIENT | Explicit consent to configure the named client; repeat or use a comma-separated list |
--no-mcp | Skip agent configuration |
--no-service | Start a detached background node instead of installing a user service |
A system without a systemd user session can use:
npx joinweave@0.1.1 --yes --no-service --no-mcp --jsonA detached node still needs to be running for doctor and strand operations. It has no OS service supervision.
Files and consent
The default native binary is ~/.weave/bin/weave. Config, identity, data and logs live under ~/.weave; the installer also creates ~/Weave. WEAVE_HOME may select a dedicated absolute workspace directory, separate from your home and the visible folder. Use the same value in every command and agent integration for that workspace.
Interactive installation offers detected MCP clients and a shell PATH entry. --yes and --json alone do not authorize either edit. For example, explicitly consent to PATH and Codex/Cursor configuration:
npx joinweave@0.1.1 --yes --path --mcp-client codex,cursor --jsonThe installer preserves unrelated configuration, refuses conflicting owned entries and symbolic links, and makes private backups beside edited config files. Open a fresh shell after accepting PATH and restart configured agent clients.
Remove the installation
npx joinweave@0.1.1 uninstall --yes --jsonUninstall removes owned service, binary, PATH and MCP entries, retaining identity and workspace data. Modified entries are preserved and reported. ~/Weave is always preserved. Only use uninstall --purge when you intend to remove the dedicated workspace and its local identity keys.
Public packaging source contains the launcher, installer, MCP server, licenses and prebuilt binaries. The native Rust implementation remains private; this release does not publish an @useweave/sdk package.
