OpenClaw Plugin Guide

Use the OpenClaw plugin when OpenClaw owns the agent, tool, and LLM lifecycle that needs NeMo Relay observability. The plugin observes supported OpenClaw plugin hooks and converts them into NeMo Relay sessions, LLM spans, tool spans, and marks that the generic NeMo Relay observability component can export as Agent Trajectory Interchange Format (ATIF) JSON, OpenTelemetry spans, OpenInference/Phoenix spans, and adaptive telemetry inputs.

This public OpenClaw plugin uses OpenClaw public hooks. It can initialize generic NeMo Relay plugin components such as observability and adaptive, but hook-backed mode does not rewrite OpenClaw tool execution, provider routing, or model requests. For middleware-backed behavior that changes execution, use the patch-based OpenClaw integration from the NeMo Relay repository.

Use this guide to install the plugin, enable it in OpenClaw, configure telemetry outputs, verify exported traces, and understand current LLM replay fidelity.

Requirements

Required:

• OpenClaw 2026.5.6 or newer.
• The OpenClaw CLI available as openclaw.

Optional:

• Node.js and npm when installing or managing the package directly.
• A Phoenix instance or OTLP collector when exporting OpenInference or OpenTelemetry spans.

Install

Install the plugin with OpenClaw so OpenClaw can register and manage it:

$
openclaw plugins install npm:nemo-relay-openclaw@0.4.0
$
openclaw gateway restart

OpenClaw uses the package nemo-relay-openclaw for installation and the plugin manifest ID nemo-relay for configuration. Use nemo-relay in plugins.allow, plugins.entries, plugins inspect, and gateway status commands.

If you manage OpenClaw plugin dependencies directly in a Node.js project, install the package with npm:

$
npm install nemo-relay-openclaw@0.4.0

Installing with npm makes the package available to that project. Use openclaw plugins install when you want OpenClaw to register and manage the plugin.

Enable and Configure the Plugin

Add the nemo-relay plugin ID to plugins.allow, grant conversation hook access, and place the OpenClaw plugin configuration under plugins.entries["nemo-relay"].config:

1
{
2
  "plugins": {
3
    "allow": ["nemo-relay"],
4
    "entries": {
5
      "nemo-relay": {
6
        "enabled": true,
7
        "hooks": {
8
          "allowConversationAccess": true
9
        },
10
        "config": {
11
          "enabled": true,
12
          "backend": "hooks",
13
          "plugins": {
14
            "version": 1,
15
            "components": [
16
              {
17
                "kind": "observability",
18
                "enabled": true,
19
                "config": {
20
                  "version": 1,
21
                  "atif": {
22
                    "enabled": true,
23
                    "agent_name": "openclaw",
24
                    "output_directory": "./nemo-relay-atif"
25
                  },
26
                  "opentelemetry": {
27
                    "enabled": false,
28
                    "transport": "http_binary",
29
                    "endpoint": "http://localhost:4318/v1/traces",
30
                    "service_name": "openclaw-nemo-relay"
31
                  },
32
                  "openinference": {
33
                    "enabled": false,
34
                    "transport": "http_binary",
35
                    "endpoint": "http://localhost:6006/v1/traces",
36
                    "service_name": "openclaw-nemo-relay"
37
                  }
38
                }
39
              },
40
              {
41
                "kind": "adaptive",
42
                "enabled": true,
43
                "config": {
44
                  "version": 1,
45
                  "agent_id": "openclaw",
46
                  "state": {
47
                    "backend": {
48
                      "kind": "in_memory",
49
                      "config": {}
50
                    }
51
                  },
52
                  "telemetry": {
53
                    "learners": ["tool_parallelism"]
54
                  }
55
                }
56
              }
57
            ]
58
          },
59
          "capture": {
60
            "includePrompts": true,
61
            "includeResponses": true,
62
            "stripToolArgs": true,
63
            "stripToolResults": true
64
          },
65
          "correlation": {
66
            "llmOutputGraceMs": 250,
67
            "recordTtlMs": 600000,
68
            "maxRecordsPerKey": 32
69
          }
70
        }
71
      }
72
    }
73
  }
74
}

This example enables local ATIF export and leaves OTLP exporters disabled until you point them at a collector or Phoenix endpoint. Remove exporter sections you do not use, or set their enabled fields to false.

• plugins.allow controls OpenClaw plugin trust and loading. Include nemo-relay when OpenClaw runs with restrictive plugin settings.
• plugins.entries["nemo-relay"].enabled controls whether OpenClaw starts this plugin entry.
• hooks.allowConversationAccess lets trusted non-bundled plugins receive conversation-sensitive hook payloads such as LLM prompts, LLM responses, agent finalization messages, and tool payloads.
• config.enabled disables or enables the NeMo Relay OpenClaw wrapper without removing the plugin entry. config.backend currently supports only hooks.
• config.plugins is the generic NeMo Relay plugin configuration document. Use this object to configure built-in components such as observability and adaptive.
• config.plugins.components[].config.atif writes ATIF trajectory JSON files. Set output_directory to the directory where OpenClaw should write files.
• config.plugins.components[].config.opentelemetry sends generic OTLP spans to an OpenTelemetry collector when enabled is true.
• config.plugins.components[].config.openinference sends OpenInference OTLP spans to Phoenix or another OpenInference-compatible collector when enabled is true.
• config.plugins.components[] entries with kind: "adaptive" initialize the Adaptive plugin. In hook-backed OpenClaw mode, adaptive telemetry can consume replayed NeMo Relay events, while request-rewrite features such as adaptive hints require a managed execution path.
• config.capture controls prompt, response, tool argument, and tool result capture. Tool arguments and tool results are stripped by default because they often contain user data, local paths, tokens, or large payloads.
• config.correlation controls bounded in-memory hook correlation. By default, the plugin waits 250 ms for a matching llm_input after an llm_output, keeps correlation records for 600 seconds, and keeps at most 32 records per correlation key.

Restart the gateway after changing plugin configuration:

$
openclaw gateway restart

Configuration Key Names

The OpenClaw wrapper owns enabled, backend, capture, and correlation. The top-level plugins object inside the wrapper is the generic NeMo Relay plugin configuration document.

Missing observability sections are disabled. Plugin-host validation or initialization errors degrade the NeMo Relay runtime as a whole, and the status method reports configured output health from the generic observability component. See Observability Configuration for the complete observability component schema and exporter-specific fields.

Verify the Integration

Inspect the plugin runtime:

$
openclaw plugins inspect nemo-relay --runtime --json

This verifies that the plugin package is installed, enabled, importable, and exposes its config schema. It does not prove that every hook and gateway method surface is active in a running gateway.

Run an OpenClaw session with the plugin enabled, then verify the configured sink:

• ATIF: confirm JSON files appear in the configured config.plugins.components[].config.atif.output_directory.
• OpenTelemetry: confirm spans arrive at the configured OTLP collector.
• OpenInference: confirm spans arrive at the configured OpenInference/Phoenix endpoint.

The plugin also registers the operator.admin scoped gateway method nemoRelay.status. If your CLI is already paired with admin-capable gateway access, run:

$
openclaw gateway call nemoRelay.status --json

Otherwise, pass your normal admin-capable gateway auth options:

$
openclaw gateway call nemoRelay.status --token "$OPENCLAW_GATEWAY_TOKEN" --json

If OpenClaw requests a device scope upgrade for operator.admin, approve it through the normal OpenClaw device approval flow and retry the status call.

The status response reports backend state, output health for atif, otel, and openInference, replay counters, and the latest degraded or unavailable reason when present.

Runtime Mapping

The plugin maps supported OpenClaw hook events into NeMo Relay telemetry and adaptive inputs without changing OpenClaw execution behavior.

It does not change OpenClaw tool execution, provider routing, policy decisions, or provider request payloads.

LLM Replay Fidelity

OpenClaw currently exposes request, response, message-write, and provider timing details through separate hook events. The plugin correlates those events within the same session, provider, model, and run.

When model timing cannot be safely paired with an assistant turn, the plugin emits diagnostic marks instead of inventing latency. This keeps traces honest and makes current fidelity boundaries explicit.

When OpenClaw provides usage data, the plugin maps input, output, total, cache read, cache write, and cost fields into OpenInference-friendly usage fields.

Troubleshooting

If the plugin does not load:

• verify the package was installed with openclaw plugins install
• verify plugins.allow includes nemo-relay
• verify plugins.entries["nemo-relay"].enabled is not disabled
• restart the gateway after config changes

If conversation payloads are missing:

• verify hooks.allowConversationAccess is enabled for the plugin
• verify the OpenClaw session emits the relevant LLM, message-write, and tool hooks

If tool spans exist but LLM spans are incomplete:

• verify llm_input and llm_output hooks are emitted
• verify before_message_write hooks are emitted when relying on assistant-turn replay
• verify model_call_started and model_call_ended hooks are emitted when timing attribution is expected
• check diagnostic marks for ambiguous or unpaired timing records

If no export output appears:

• verify config.plugins.components[].config.atif.output_directory, config.plugins.components[].config.opentelemetry.endpoint, or config.plugins.components[].config.openinference.endpoint
• verify the configured collector or output directory is reachable
• verify session end or gateway stop hooks fired so pending replay state can drain

If ambiguous timing marks appear, treat them as expected conservative behavior. The plugin avoids attaching unsafe latency when multiple timing candidates could match the same assistant turn.

Known Limitations

Current OpenClaw public hooks are separate event streams, so some LLM timing attribution is best-effort. If a matching request hook is missing, the plugin may replay an LLM output with a placeholder request after the configured grace window. If timing is ambiguous, the plugin emits diagnostic marks instead of unsafe latency.