OpenClaw | Opik Documentation

OpenClaw can send trace data to Opik through the community plugin package @opik/opik-openclaw.

This integration captures:

LLM spans (llm_input, llm_output)
Tool spans (before_tool_call, after_tool_call)
Agent-level run metadata (agent_end, usage/cost diagnostics)

Prerequisites

OpenClaw version 2026.3.2 or newer.
Opik project/workspace details (for cloud or enterprise deployments).

Setup

1. Install the plugin

openclaw plugins install @opik/opik-openclaw

2. Configure the plugin

openclaw opik configure

This command validates your Opik URL, validates API key access (when required), enables the plugin, and writes plugin-scoped config.

3. Check status and restart the OpenClaw gateway

openclaw opik status
openclaw gateway restart

Advanced configuration (manual JSON)

Use this only when you need explicit checked-in or templated plugin configuration. For the latest plugin-specific options, see opik-openclaw.

Add this to your OpenClaw config:

{
  "plugins": {
    "entries": {
      "opik": {
        "enabled": true,
        "config": {
          "enabled": true,
          "apiUrl": "https://www.comet.com/opik/api",
          "apiKey": "your-api-key",
          "projectName": "openclaw",
          "workspaceName": "default",
          "tags": ["openclaw"]
        }
      }
    }
  }
}

Environment variable fallbacks are also supported:

OPIK_API_KEY
OPIK_URL_OVERRIDE
OPIK_PROJECT_NAME
OPIK_WORKSPACE

Validate setup

1. Check plugin status

openclaw opik status

2. Send a message and verify traces in Opik

Send a message through OpenClaw and verify traces appear in the configured Opik project dashboard.

Known limitation

Some OpenClaw embedded execution paths currently emit after_tool_call without a sessionKey. The plugin uses a best-effort fallback (single active trace or most recent active session), which can mis-correlate tool spans when multiple sessions run concurrently.

Next step

For OTEL-native pipelines, see OpenTelemetry integration.