Quickstart

Weave adds a team of agents (Loom, Tapestry, Shuttle, Pattern, Thread, Spindle, Weft, and Warp) to the coding-agent harness you already use. Installing it is one step on OpenCode and three on Claude Code.

Add the adapter to the plugin list in your project’s opencode.json (or ~/.config/opencode/opencode.json), then restart OpenCode:

{
  "plugin": ["@weaveio/weave-adapter-opencode@0.2.0"]
}

OpenCode downloads the plugin itself. See Install for OpenCode.

Add the adapter to the plugins list (plural) in your project’s opencode.jsonc (or ~/.config/opencode/opencode.jsonc), then start opencode2:

{
  "plugins": ["@weaveio/weave-adapter-opencode2@0.2.0"]
}

OpenCode 2 downloads the plugin itself. See Install for OpenCode 2.

Install the CLI with Bun, generate the plugins in your project, and start Claude Code with them:

bun add --global @weaveio/weave-cli@0.2.0
weave compose --adapter claude-code --init
claude --plugin-dir ./weave-bootstrap-plugin --plugin-dir ./.weave/plugins/claude-code

See Install for Claude Code.

You don’t need any configuration to start: without a .weave config, Weave registers its builtin agents. Start a session on Loom (on OpenCode 2 and Claude Code new sessions already start on Loom) and describe what you want. Loom answers simple questions itself, delegates bounded work to Shuttle and the other specialists, and sends plan-sized work to Pattern. To execute a saved plan, run /weave:start.

See Agents for what each agent does.

To add your own agents or categories, or to change a builtin’s prompt or models, create a .weave/config.weave in your project with the Weave CLI. The CLI runs on Bun. Use bunx to run it without installing it:

bunx @weaveio/weave-cli@0.2.0 init --scope local --yes

This creates:

• .weave/config.weave: your configuration file. The starter leaves the builtin agents exactly as they ship and shows how to extend them.
• .weave/prompts/: a directory for prompt files.

weave init can also set up a harness for you with --harness opencode, --harness opencode2, or --harness claude-code: it adds the pinned plugin entry for OpenCode or OpenCode 2, or runs the compose step for Claude Code. Without --harness, --yes writes only the Weave config.

Check your configuration, list the agents it defines, and see the exact prompt an agent receives:

bunx @weaveio/weave-cli@0.2.0 validate
bunx @weaveio/weave-cli@0.2.0 prompt list
bunx @weaveio/weave-cli@0.2.0 prompt inspect loom

weave validate checks the merged project and user config, and reports any agent the harness adapters can’t register. weave prompt inspect prints the prompt exactly as the harness receives it, after your prompts, appends, and delegation targets are composed.

Restart your harness (or, on Claude Code, start a new session) after you change .weave/config.weave.

• DSL Configuration: the .weave syntax
• Categories: route work to domain-specific shuttles
• Model Resolution: how each harness picks a model for an agent
• Troubleshooting