Install for Claude Code

Claude Code loads Weave as two plugin directories that the Weave CLI generates in your project. Unlike OpenCode, Claude Code needs the CLI installed.

• Claude Code
• Bun. The Weave CLI runs on Bun, not Node.js.

1. Install the Weave CLI globally:

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

2. In your project, generate the Claude Code plugins:

   weave compose --adapter claude-code --init

   This writes two directories:

   • .weave/plugins/claude-code/: the agents (loom.md, shuttle.md, …), the /weave:start command, and a settings.json that makes Loom the main agent.
   • weave-bootstrap-plugin/: a SessionStart hook that runs weave compose --adapter claude-code at the start of every session, so the agents follow your .weave config. This hook is why the CLI must be installed globally.

   You don’t need a .weave config: without one, Weave generates its builtin agents. To customize them, run weave init --scope local --yes first, or later, and edit .weave/config.weave. weave init --harness claude-code writes the config and runs this compose step in one go.

3. Start Claude Code with both plugin directories:

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

Add .weave/plugins/ to your .gitignore: it is generated.

The session’s main agent is Loom, and the agent list includes the Weave agents as weave:loom, weave:shuttle, weave:pattern, and so on. Ask Loom for a change and it delegates to them, for example to weave:shuttle.

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 you change your .weave configuration, start a new session, or run /reload-plugins, so Claude Code picks up the regenerated files. The /weave:start command (with /start-work as a compatibility alias) begins plan-based work.

The Weave CLI is published on two npm channels:

• latest: Stable releases (recommended)
• next: Pre-releases for trying upcoming changes

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