Weave Claude Code Plugin

Track Claude Code sessions in Weave for observability and debugging. Every session, turn, tool call, and subagent is automatically logged as a structured trace — no code changes required.

Quick Start

1. Install the CLI

npm install -g weave-claude-code

2. Run the installer

weave-claude-code install

This will:

• Create ~/.weave-claude-code/settings.json
• Register the plugin in Claude Code
• Prompt for your Weave project (entity/project) and W&B API key if not already set

Your W&B API key is available at https://wandb.ai/authorize.

For CI, bootstrap scripts, or other automated systems, you can skip prompts:

WEAVE_PROJECT=my-entity/my-project \
WANDB_API_KEY=<your-api-key> \
weave-claude-code install --non-interactive

In non-interactive mode, the installer still creates config, registers the Claude marketplace, and installs the plugin. It does not prompt for missing values. Instead, it:

• Uses WEAVE_PROJECT and WANDB_API_KEY from the environment when present
• Warns and continues if either value is missing
• Leaves environment-provided values in the environment rather than writing them into settings.json

By default, claude plugin marketplace add clones wandb/weave-claude-code from GitHub. In CI or container sandboxes without git/SSH access to GitHub, pass --source=local to register the marketplace from the npm-installed tree on disk instead:

npm install -g weave-claude-code
weave-claude-code install --non-interactive --source=local

--source=local requires the package to be installed globally via npm first (it reads from $(npm root -g)/weave-claude-code). Upgrades follow the npm cadence; the marketplace ref drift check is skipped for local sources.

3. Restart or launch Claude Code

If Claude Code is already running, reload plugins from inside the session:

/reload-plugins

Otherwise, launch Claude Code from any folder:

claude

Sessions are traced automatically from this point, across all Claude Code sessions on this machine. Tracing is not scoped to a single project. To stop tracing, run weave-claude-code uninstall.

Open your Weave project to see them.

Data Disclosure

This plugin sends Claude Code session data to W&B Weave.

That data can include sensitive content, including:

• user prompts
• Claude responses
• tool inputs
• tool outputs
• file paths and file contents read by Claude Code tools
• shell commands and shell output
• fetched URLs and fetched page content

If Claude Code accesses secrets, credentials, proprietary source code, personal
data, or other confidential material during a session, that information may be
logged to W&B Weave as part of the trace.

PII scrubbing and sensitive-data redaction are not yet implemented in the
current version. If you cannot send this data to W&B Weave under your security
or compliance requirements, do not install or enable this plugin yet.

Configuration

# Show all current settings (env-var overrides are flagged in the output)
weave-claude-code config show

# Read a single setting (resolves env-var overrides)
weave-claude-code config get weave_project

# Set your Weave project
weave-claude-code config set weave_project my-entity/my-project

# Set your W&B API key
weave-claude-code config set wandb_api_key <your-api-key>

# (Optional) Customize the agent name shown in Weave's Agents view (default: claude-code)
weave-claude-code config set agent_name my-team-bot

You can also set these via environment variables — they take precedence over the settings file:

export WEAVE_PROJECT=my-entity/my-project
export WANDB_API_KEY=<your-api-key>
export WEAVE_AGENT_NAME=my-team-bot

This is especially useful with weave-claude-code install --non-interactive, where the installer checks these variables instead of prompting.

Sending Traces to a Dedicated or Private W&B Instance

If you use W&B Dedicated Cloud or a self-hosted instance, set WANDB_BASE_URL to point the plugin at your deployment before launching Claude Code:

export WANDB_BASE_URL=https://your-instance.wandb.io

On SaaS, leave WANDB_BASE_URL unset (traces go to https://trace.wandb.ai). Setting it to the SaaS API host https://api.wandb.ai is handled automatically, since that host has no trace-ingest route. To send traces somewhere other than the wandb API host, set WF_TRACE_SERVER_URL, which takes precedence over WANDB_BASE_URL.

Important: The plugin runs a background daemon that creates the Weave client at startup. If WANDB_BASE_URL is set after the daemon is already running, it will have no effect — the daemon must be restarted with the variable present in its environment.

Workaround if the daemon is already running:

1. Shut down the daemon:

   printf '{"command":"shutdown"}' | nc -U -w1 ~/.weave-claude-code/daemon.sock
   

2. Point the plugin at your instance using either approach:

   Option A — environment variable (takes effect for the current shell session):

   export WANDB_BASE_URL=https://your-instance.wandb.io
   

   Option B — wandb login (persists across sessions via ~/.config/wandb/settings):

   wandb login --host https://your-instance.wandb.io
   

   This writes the host URL to $HOME/.config/wandb/settings, which the Weave client reads automatically — no env var required on future launches.

3. Relaunch Claude Code — the daemon will start fresh and pick up the correct URL:

   claude
   

Check Status

weave-claude-code status

Each line shows ✓ (OK), ✗ (action needed), or - (not yet active but not an error).

If sessions are not appearing in Weave, check the daemon log for errors:

weave-claude-code logs              # last 50 lines (default)
weave-claude-code logs --tail 200   # last N lines
weave-claude-code logs --follow     # tail -f

The log file is also directly at ~/.weave-claude-code/logs/daemon.log.

For more verbose daemon output while diagnosing an issue, enable debug mode:

weave-claude-code config set debug true
# or, just for the current shell session:
export WEAVE_CLAUDE_DEBUG=1

Skills

Once the plugin is installed, three skills are available directly inside any Claude Code session. They use a /weave:weave-* naming pattern (rather than the shorter /weave:install form) to avoid colliding with Claude Code's built-in skills.

/weave:weave-install

Walks through the full installation and configuration flow interactively. Use this on a fresh machine or to diagnose a broken setup. Claude will check for the CLI, run the installer, prompt for missing config values, and verify everything is working.

/weave:weave-install

/weave:weave-status

Checks the current plugin status and explains any issues. Equivalent to running weave-claude-code status but Claude interprets the output and tells you exactly what to fix.

/weave:weave-status

/weave:weave-config

Read or update plugin configuration without leaving Claude Code.

# Show current config
/weave:weave-config

# Set a value directly
/weave:weave-config set weave_project my-entity/my-project
/weave:weave-config set wandb_api_key <your-api-key>

What Gets Traced

The plugin emits OTel spans that follow the GenAI semantic
conventions and ships
them to the Weave Agents observability backend (/agents/otel/v1/traces).
Each user prompt produces one OTel trace (the "turn"); multi-turn
conversations are stitched together server-side via
gen_ai.conversation.id, which is set to the Claude Code session id on
every span in the turn.

invoke_agent claude-code                  (root — one trace per user prompt)
├─ chat <model>                           (each LLM API call within the turn)
├─ execute_tool <tool_name>               (each tool call: Read, Bash, Grep, ...)
└─ invoke_agent <subagent_type>           (subagent dispatched via the `Agent` tool)
   ├─ chat <model>                        (subagent LLM calls)
   └─ execute_tool <tool_name>            (tools the subagent ran)

Subagents (dispatched via Claude Code's Agent tool) are emitted as their
own nested invoke_agent span — a direct child of the turn span, sibling
of any regular tool calls — not as an execute_tool Agent span. This
matches the Weave Agents chat view's reference structure, where nested
invoke_agent spans render as an agent_start lifecycle marker for the
subagent. The spawning tool_use_id is preserved on the inner
invoke_agent span as weave.claude_code.subagent.spawning_tool_call_id.

Permission requests appear as weave.permission_request span events on the
parent execute_tool span; context-window compaction is stamped as
weave.compaction.{summary,items_before,items_after} attributes on the
turn span open at compaction time (or the next turn if compaction fires
between turns).

Each span includes per-call token usage (gen_ai.usage.input_tokens,
gen_ai.usage.output_tokens, cache and reasoning token counts), model name
(gen_ai.request.model), tool inputs and outputs
(gen_ai.tool.call.arguments, gen_ai.tool.call.result), timing, and the
textual content of prompts and assistant messages
(gen_ai.input.messages, gen_ai.output.messages).

Important: tool inputs and outputs may contain sensitive information. In
practice this can include file contents, command output, URLs, fetched content,
and other data handled by Claude Code during a session. That information is sent
to W&B Weave. PII scrubbing/redaction is planned for a future release, but is
not available today.

Uninstall

weave-claude-code uninstall

Pass --keep-logs to preserve the log directory.

Releasing

This package is published to npm and pinned in the Claude Code marketplace
to a specific release tag rather than the repository default branch. New
releases are cut via two GitHub Actions:

1. Version Bump — dispatched with a version like 0.1.2. Bumps the
   pinned version across the repo, pins the marketplace to the resulting
   commit SHA, and creates and pushes the matching v0.1.2 tag.
2. Publish Package — dispatched with the tag (e.g. v0.1.2). Verifies
   the tag is consistent and not already published, then builds and
   publishes to npm.