coreweave/forge-agent-lens-for-openclaw

coreweave/forge-agent-lens-for-openclaw

Description: CoreWeave Forge Agent Lens Integration for OpenClaw

Language: TypeScript

License: Apache-2.0

Stars: 4

Forks: 0

Open issues: 5

Created: 2026-05-02T23:32:50Z

Pushed: 2026-10-02T21:38:37Z

Default branch: main

Fork: no

Archived: no

README:

forge-agent-lens-for-openclaw


OpenClaw plugin for tracing agent runs, model calls, tool calls, tokens, and costs in CoreWeave Forge.

> [!WARNING] > captureContent defaults to true. Prompts, replies, and tool inputs and > results are sent unredacted to W&B. Set it to false to record only trace > structure, tokens, and costs.

Tracing SDK

Tracing uses @coreweave/forge-sdk/agentlens/tracing. Every turn, chat, tool, and subagent span carries forge.integration.name = forge-agent-lens-for-openclaw and forge.integration.version. The OTLP resource reports wandb.sdk.name = forge. Plugin configuration and credential precedence are unchanged.

Requirements

• Node.js >= 22.14.0
• OpenClaw >= 2026.4.25
• A W&B account and project

Migration from weave-openclaw

The plugin ID and status command are now forge and /forge status. Disable and uninstall the old weave plugin before installing this package so both integrations do not export duplicate traces. Move the settings from plugins.entries.weave to plugins.entries.forge, and replace weave with forge in plugins.allow. Configuration fields and W&B credentials are unchanged. There is no legacy plugin-ID or command alias.

Span attributes moved from weave.* to forge.*; for example, weave.outcome is now forge.outcome. Agent version, ID, and description use the gen_ai.agent.* semantic conventions, and weave.source was removed. Only weave.compaction.* keeps its name, because the Weave backend reads it. W&B API and environment names and the /weave/agents dashboard route are unchanged.

Setup

The commands below target the renamed release; this local change does not publish npm or ClawHub packages. Development uses the published @coreweave/forge-sdk@0.1.0-beta.0 prerelease, pinned exactly for reproducibility.

Install the plugin:

openclaw plugins install clawhub:@coreweave/forge-agent-lens-for-openclaw

Export a W&B API key:

export WANDB_API_KEY=

Add the plugin to ~/.openclaw/openclaw.json:

{
diagnostics: { enabled: true },
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://wandb.ai///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.

See the full setup guide and ClawHub listing.

Configuration

Only entity and project are required. Everything else has a sensible default.

{
plugins: {
entries: {
forge: {
enabled: true,
config: {
entity: "your-team", // your W&B team or username
project: "your-project", // your W&B project name

// Leave apiKey out to use the WANDB_API_KEY environment variable.
// File and exec SecretRefs also work with a configured OpenClaw
// secret provider.
// A plain key string works too, but keeping secrets out of config is safer:
// 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:

1. apiKey SecretRef 2. Plain apiKey 3. WANDB_API_KEY 4. ~/.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

Development

npx pnpm@9 install --frozen-lockfile
npx pnpm@9 check

openclaw plugins install --link .
openclaw gateway restart
openclaw plugins inspect forge --runtime --json

Contributing

See [CONTRIBUTING.md](./CONTRIBUTING.md). Contributions require agreeing to the [CoreWeave CLA](./CLA.md).

License

[Apache License 2.0](./LICENSE)