Install for Claude Code

• Bun runtime
• Claude Code

1. Install the Weave CLI globally:

bun add --global @weaveio/weave-cli@latest

See the CLI reference for more details.

2. Initialize Weave:

weave init --scope local --yes

See the DSL Configuration guide for configuration syntax.

3. Compose the Claude Code adapter configuration:

weave compose --adapter claude-code --init

This generates agents, composed prompts, model aliases, and tool lists under .weave/plugins/claude-code/. It also creates a weave-bootstrap-plugin/ directory with plugin.json, compose.yaml, and templates that rerun composition at session start.

4. Launch Claude Code with the generated plugin directories:

claude --plugin-dir ./weave-bootstrap-plugin --plugin-dir ./.weave/plugins/claude-code

Claude Code support is file materialization only. The generated files provide agents, prompts, model aliases, tool lists, category shuttles, and the /weave:start plan-entry command. They do not provide a durable workflow runtime.

This is deliberately not a claim of runtime parity with other adapters. Generated files cannot provide durable workflow scheduling, lifecycle observation, idle continuation, compaction recovery, analytics, or runtime-backed eval control.

After making changes to your .weave configuration, you must reload plugins or start a new session for Claude Code to pick up the updated generated files. The /weave:start command (with /start-work as a compatibility alias) is available to begin plan-based work.

Weave is available on multiple release channels:

• latest: Stable releases (recommended)
• next: Pre-release versions with upcoming features
• nightly: Bleeding-edge builds from the main branch

To install a specific channel, specify it in the install command:

bun add --global @weaveio/weave-cli@next