Installation
Install the Weave plugin for Fabric — fabriccode install-weave (recommended), shell installer, PowerShell installer, or manual setup. Plus uninstall, troubleshooting, and a blank-screen recovery procedure.
Weave is published on npm as @fabriccode/weave and installs as a Fabric plugin. There are three install paths depending on your environment; the first is recommended.
Prerequisites
-
Node.js + npm — used to install the Fabric Code CLI globally.
-
Fabric Code CLI v7.0.50 or later — provides the
install-weavesubcommand. Install or upgrade it with:npm i -g @fabriccode/cli@latestVerify with
fabriccode --version. If you already have an older Fabric Code CLI, the same command upgrades it in place.
Option 1 — Built-in CLI (recommended)
The fastest install on any platform — once fabriccode is on your PATH:
fabriccode install-weaveThis command:
- ✅ detects your Fabric configuration directory
- ✅ adds
@fabriccode/weaveto thepluginarray in~/.config/fabric/fabric.jsonc - ✅ creates
~/.config/fabric/weave-fabric.jsoncwith sensible defaults - ✅ offers to restart Fabric so the plugin activates immediately
When Fabric next launches it auto-installs the npm package and registers the agents.
Option 2 — Shell installer
If you can't run fabriccode install-weave (older Fabric Code CLI, scripted setup, restricted environment) you can use the standalone installer.
macOS / Linux
curl -fsSL https://raw.githubusercontent.com/Fabric-Pro/fabric-weave/main/script/install.sh | bashWindows (PowerShell)
irm https://raw.githubusercontent.com/Fabric-Pro/fabric-weave/main/script/install.ps1 | iexBoth installers do the same work as fabriccode install-weave — edit fabric.jsonc, drop in a default weave-fabric.jsonc, and prompt you to restart Fabric.
Option 3 — Manual
For air-gapped machines or fully custom setups:
1. Add the plugin to ~/.config/fabric/fabric.jsonc:
{
"plugin": ["@fabriccode/weave"]
}2. (Optional) Seed a config file at ~/.config/fabric/weave-fabric.jsonc. Weave works with zero configuration; only create this file if you want to override defaults — see Configuration.
3. Restart Fabric. It auto-installs npm plugins on startup and registers the new agents. You should see @loom, @tapestry, @pattern, @thread, @spindle, @weft, @warp, and @shuttle in the @ mention menu.
Verify the install
After Fabric restarts, open a new conversation and type @. You should see Weave's agents at the top of the mention list. Try:
@loom what's in this repo?Loom should respond as the team lead and may dispatch to @thread for a codebase scan.
Updating
Weave follows semver and publishes patch releases regularly. When Fabric starts it pulls the latest version compatible with the version range in your fabric.jsonc. To pin a version:
{
"plugin": ["@fabriccode/weave@0.8.6"]
}To force a re-install of the latest:
rm -rf ~/.config/fabric/node_modules/@fabriccode/weave
# then restart FabricUninstall
Step 1 — Remove from fabric.jsonc
Delete the @fabriccode/weave entry from the plugin array:
{
"plugin": []
}Step 2 — (Optional) Clean up project artifacts
# Plans + execution state for the current project
rm -rf .weave/
# Project-level Weave config, if you used one
rm -f .fabric/weave-fabric.jsonc .fabric/weave-fabric.jsonStep 3 — (Optional) Remove user-level config
rm -f ~/.config/fabric/weave-fabric.jsonc ~/.config/fabric/weave-fabric.jsonRestart Fabric to drop the agents from the UI.
Troubleshooting
| Symptom | Fix |
|---|---|
404 Not Found from npm | Confirm the package name is @fabriccode/weave (note the @fabriccode scope, not @fabric). |
| Package not found right after publishing | npm propagation can take a few minutes — wait and retry. |
| Blank screen after restart | Auto-install may have failed silently. See Blank-screen recovery below. |
| Agents still missing after restart | Check ~/.config/fabric/fabric.jsonc actually contains the @fabriccode/weave entry in the plugin array. |
| Want to test a local checkout instead of npm | Build with bun run script/build.ts and add "plugin": ["file:/abs/path/to/fabric-weave"]. |
Blank-screen recovery
If Fabric shows a blank screen after restart, the plugin probably didn't auto-install (this happens when ~/.config/fabric/package.json has a stale dependency that blocks bun). Install the three packages by hand:
cd /tmp
# Weave itself
npm pack @fabriccode/weave@latest
mkdir -p ~/.config/fabric/node_modules/@fabriccode/weave
tar xzf fabriccode-weave-*.tgz -C ~/.config/fabric/node_modules/@fabriccode/weave --strip-components=1
# Plugin runtime
npm pack @fabriccode/plugin@latest
mkdir -p ~/.config/fabric/node_modules/@fabriccode/plugin
tar xzf fabriccode-plugin-*.tgz -C ~/.config/fabric/node_modules/@fabriccode/plugin --strip-components=1
# SDK
npm pack @fabriccode/sdk@latest
mkdir -p ~/.config/fabric/node_modules/@fabriccode/sdk
tar xzf fabriccode-sdk-*.tgz -C ~/.config/fabric/node_modules/@fabriccode/sdk --strip-components=1Then restart Fabric.
Next: Configuration walks through every option in weave-fabric.jsonc.
Weave
Lean Fabric plugin with multi-agent orchestration. Eight specialised agents — Loom, Tapestry, Pattern, Thread, Spindle, Weft, Warp, Shuttle — with a Plan → Review → Execute workflow.
Configuration
Configure Weave with weave-fabric.jsonc — per-agent model overrides, category-based dispatch, hook/tool/skill toggles, background concurrency, skill discovery paths, and experimental settings. Layered user → project merging.