Linux
Download the latest Weave release and run it. The Linux build includes the full sandboxing stack (Bubblewrap + OverlayFS).
# Binary - Make the binary executable and run it
chmod +x weave-x86_64
./weave-x86_64
# Deb - Install via dpkg or software manager
sudo dpkg -i ./weave-x86_64.deb
# RPM - Install via dnf/yum or software manager
sudo dnf install ./weave-x86_64.rpm
The Weave binary requires webkit2gtk-4.1. Install it with your package manager if it isn't already present — e.g. apt install libwebkit2gtk-4.1-0 or dnf install webkit2gtk4.1.
For the sandbox to work, your system needs
bubblewrap installed and a kernel that allows unprivileged user namespaces (the
default on most modern distributions). If it isn't already present, install it with your
package manager — e.g. apt install bubblewrap or
dnf install bubblewrap.
Linux-only features: Bubblewrap tool sandboxing and OverlayFS write review require Linux and are not present in Weave Lite for macOS.
macOS (Weave Lite)
Download Weave Lite, drag it to Applications, and launch. Weave Lite shares the chat and Weaves workflow but does not include the Linux sandboxing features — tools run directly on the host, confined to the project directory by path checks rather than a kernel sandbox.
“Weave can’t be opened” on macOS? The macOS builds are self-signed (there's
no Apple Developer account behind them), so if you install from the .dmg rather
than running the bare binary, Gatekeeper quarantines the app. Clear the quarantine flag once
and it'll open normally:
# Remove the quarantine attribute, then launch as usual
xattr -dr com.apple.quarantine /Applications/Weave.app
This is expected for self-signed apps and only needs to be done once after install (or after updating to a new build).
Where Weave keeps its data
Everything is stored locally. Settings, projects, chats, and weaves live in a single SQLite database, and skills are plain Markdown files:
- Linux:
~/.config/weave/(data.dbandskills/) - macOS:
~/Library/Application Support/weave/
Override this with --config-dir /path/to/dir (or -c) on the command
line, or the WEAVE_CONFIG_DIR environment variable if a flag isn't convenient —
useful for running isolated profiles or a portable install. The flag takes precedence over the
environment variable.
First launch
On first run, add a provider and agent so Weave can reach a model, then create a project. The Quickstart walks through this end to end.
