How do I install the Weave Config skill?

Run npx skillmds@latest add wandb/weave-config in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Weave Config safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Weave Config?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Weave Config free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Weave Config?

wandb (@wandb) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Weave Config by wandb — Agent Skill

Name: Weave Config
Author: wandb

Weave Config

This skill should be used when the user wants to "configure weave", "set weave project", "change weave project", "set wandb api key", "update weave settings", "show weave config", "change weave configuration", "restart the weave daemon", "apply weave config changes", "restart weave to pick up changes", or needs to read or update any Weave Claude Code plugin settings.

wandb df72152 2.4 KB Updated Sep 17, 2026

File contents

Weave Claude Code Plugin — Config

Read and update configuration for the Weave Claude Code plugin.

Determine Intent

If the user invoked this skill with arguments (e.g., /weave:weave-config set weave_project entity/project), execute the corresponding command directly. Otherwise, show the current configuration first and then ask what they want to change.

Show Current Config

Run:

weave-claude-code config show

This displays all settings and their sources (settings file vs environment variable).

Set a Value

To update a setting:

weave-claude-code config set KEY VALUE

Writable keys:

Key	Format	Example
`weave_project`	`entity/project`	`my-org/my-project`
`wandb_api_key`	string	`abc123...`
`agent_name`	string	`my-team-bot`
`debug`	`true` / `false`	`true`
`daemon_socket`	file path	`~/.weave-claude-code/daemon.sock`

Validation notes:

weave_project must contain a / (entity/project format). Find your entity name at https://wandb.ai.
wandb_api_key is available at https://wandb.ai/authorize.
agent_name is the name shown for the top-level agent in Weave's Agents view. It must not be empty; surrounding whitespace is trimmed. Defaults to claude-code when unset.
Environment variables WEAVE_PROJECT, WANDB_API_KEY, and WEAVE_AGENT_NAME take precedence over settings file values when set.

Get a Single Value

To read one setting:

weave-claude-code config get KEY

After Changes

After setting weave_project, wandb_api_key, or agent_name, run weave-claude-code config show to confirm the new value.

The daemon reads these once at startup and persists across Claude Code sessions, so a change is not picked up by a daemon that is already running. Apply it with:

weave-claude-code restart

This stops the running daemon and starts a fresh one. (If none is running, the next Claude Code session starts one with the updated config.)

---name: weave-configdescription: This skill should be used when the user wants to "configure weave", "set weave project", "change weave project", "set wandb api key", "update weave settings", "show weave config", "change weave configuration", "restart the weave daemon", "apply weave config changes", "restart weave to pick up changes", or needs to read or update any Weave Claude Code plugin settings.---# Weave Claude Code Plugin — ConfigRead and update configuration for the Weave Claude Code plugin.## Determine IntentIf the user invoked this skill with arguments (e.g., `/weave:weave-config set weave_project entity/project`), execute the corresponding command directly. Otherwise, show the current configuration first and then ask what they want to change.## Show Current ConfigRun:```bashweave-claude-code config show```This displays all settings and their sources (settings file vs environment variable).## Set a ValueTo update a setting:```bashweave-claude-code config set KEY VALUE```Writable keys:| Key | Format | Example ||-----|--------|---------|| `weave_project` | `entity/project` | `my-org/my-project` || `wandb_api_key` | string | `abc123...` || `agent_name` | string | `my-team-bot` || `debug` | `true` / `false` | `true` || `daemon_socket` | file path | `~/.weave-claude-code/daemon.sock` |**Validation notes:**- `weave_project` must contain a `/` (entity/project format). Find your entity name at https://wandb.ai.- `wandb_api_key` is available at https://wandb.ai/authorize.- `agent_name` is the name shown for the top-level agent in Weave's Agents view. It must not be empty; surrounding whitespace is trimmed. Defaults to `claude-code` when unset.- Environment variables `WEAVE_PROJECT`, `WANDB_API_KEY`, and `WEAVE_AGENT_NAME` take precedence over settings file values when set.## Get a Single ValueTo read one setting:```bashweave-claude-code config get KEY```## After ChangesAfter setting `weave_project`, `wandb_api_key`, or `agent_name`, run `weave-claude-code config show` to confirm the new value.The daemon reads these once at startup and persists across Claude Code sessions, so a change is **not** picked up by a daemon that is already running. Apply it with:```bashweave-claude-code restart```This stops the running daemon and starts a fresh one. (If none is running, the next Claude Code session starts one with the updated config.)

Frequently asked questions