CoreWeave Forge
OpenClaw plugin that traces agent sessions to CoreWeave Forge for observability and debugging.
Install
Current stable OpenClaw · through 2026.10.4
openclaw plugins install clawhub:@coreweave/forge-agent-lens-for-openclawUpdated OpenClaw · main/dev
openclaw plugins install @coreweave/forge-agent-lens-for-openclawRequires a build with ClawHub-default support.
forge-agent-lens-for-openclaw
OpenClaw plugin for tracing agent runs, model calls, tool calls, tokens, and costs in CoreWeave Forge.
[!WARNING]
captureContentdefaults totrue. Prompts, replies, and tool inputs and results are sent unredacted to W&B. Set it tofalseto record only trace structure, tokens, and costs.
Requirements
- Node.js 24.16+ or 26.1+
- OpenClaw >= 2026.9.8
- A W&B account and project
Setup
Install the plugin:
openclaw plugins install clawhub:@coreweave/forge-agent-lens-for-openclaw
Export a W&B API key:
export WANDB_API_KEY=<your-key>
Add the plugin to ~/.openclaw/openclaw.json:
{
plugins: {
allow: ["forge"],
entries: {
forge: {
enabled: true,
config: { entity: "your-team", project: "your-project" },
hooks: { allowConversationAccess: true },
},
},
},
}
Restart the gateway if needed:
openclaw gateway restart
Run /forge status in a chat. When it reports running, view traces at:
https://forge.coreweave.com/wandb/<entity>/<project>/weave/agents
hooks.allowConversationAccess: true allows prompts, replies, and per-call
token counts. Without it, trace structure, tool calls, and run totals still
work. diagnostics.enabled: false disables tracing.
Configuration
Only entity and project are required.
{
plugins: {
entries: {
forge: {
enabled: true,
config: {
entity: "your-team", // your W&B team or username
project: "your-project", // your W&B project name
// Optional; see the credential lookup order below. A SecretRef keeps
// the key out of this file. A plain string also works but is discouraged:
// apiKey: "your-wandb-api-key"
apiKey: { source: "env", provider: "default", id: "WANDB_API_KEY" },
serviceName: "openclaw-agent", // shown in /forge status
// These help group and label your agents in the dashboard.
agentName: "my-agent",
agentVersion: "v1.0",
agentDescription: "What my agent does.",
// On by default. Set to false to stop recording the actual message
// text (for example, to meet a privacy or retention policy). The
// plugin records text as-is and does not hide sensitive values, so
// remove them beforehand if you need to.
captureContent: true,
// How often (in milliseconds) traces are sent.
flushIntervalMs: 1000,
},
hooks: { allowConversationAccess: true },
},
},
},
}
Environment refs work without extra setup. File and exec refs need a matching
secrets.providers entry; see OpenClaw secrets management.
Credential lookup order:
apiKeyin the plugin config (SecretRef or plain string)WANDB_API_KEY~/.netrc
OpenClaw also loads WANDB_API_KEY from ~/.openclaw/.env. Set
WANDB_BASE_URL for dedicated or self-hosted W&B.
Troubleshooting
| Problem | Check |
|---|---|
/forge status is not running | Check entity, project, the plugin version, and gateway logs. |
| No traces | Ensure diagnostics are enabled and the configured project matches /forge status. |
| Blank messages or model calls | Set hooks.allowConversationAccess: true and restart. |
401 or 403 | Refresh the API key and confirm project access. |
404 on self-hosted W&B | Check WANDB_BASE_URL. |
| Connection or DNS error | Check gateway network, proxy, and firewall access to W&B. |
Manage the plugin
openclaw plugins update forge
openclaw plugins disable forge
openclaw plugins enable forge
openclaw plugins uninstall forge
Contributing
See CONTRIBUTING.md. Contributions require agreeing to the CoreWeave CLA.
