OpenClaw Plugin Deployment

openclaw-bonree-plugin is an OpenClaw plugin that reports AI Agent execution traces to Bonree ONE through OpenTelemetry OTLP.

It mainly covers the following runtime data:

• Gateway lifecycle
• Session lifecycle
• User messages
• LLM requests and responses
• Tool calls
• Agent execution lifecycle

Prerequisites

Before deployment, make sure the target host meets the following requirements:

• OpenClaw is already installed and the openclaw command is available in PATH
• The Bonree ONE OTLP Endpoint is reachable from the host
• The required x-br-acid account GUID has been obtained from the deployment page

Restrictions

Item	Description
Reporting protocol	Only HTTP/Protobuf is supported. HTTP/JSON and gRPC are not supported.
Tested OpenClaw version	Only tested with OpenClaw v2026.3.12, v2026.3.24, v2026.3.31, and v2026.4.9.

Install

Run the following command directly, for example:

curl -fsSL https://one.bonree.com/docs/en/en/openclaw/install.sh | bash -s -- \
--endpoint "https://oneupload.bonree.com/APM/otel" \
--account "your-accountGUID" \
--set-env-id "your-env-id" \
--set-attr "datacenter=1" \
--serviceName "your-service-name" \
--plugin-url "https://one.bonree.com/docs/en/en/openclaw/openclaw-bonree-plugin.tar.gz"

Download links:

• install.sh
• openclaw-bonree-plugin.tar.gz

Parameters

Parameter	Required	Description
--endpoint	Yes	Bonree ONE OTLP endpoint. It must be reachable from the host.
--account	Yes	Bonree ONE account GUID, mapped to x-br-acid.
--set-env-id	No	Environment ID, mapped to x-br-envid. You can find it on the Deployment Configuration -> Installation Deployment page.
--set-attr	No	Data center ID, mapped to x-br-attrs. Example: datacenter=1.
--serviceName	No	Service name. Default is openclaw-agent.
--install-dir	No	Custom OpenClaw state root. The install script appends extensions/openclaw-bonree-plugin to this path.
--plugin-url	No	Custom plugin package download URL.

Default Install Path

If --install-dir is not provided, the install script selects the target directory in the following order:

• $OPENCLAW_STATE_DIR/extensions/openclaw-bonree-plugin
• ~/.openclaw/extensions/openclaw-bonree-plugin

Config Written to OpenClaw

After installation, the script updates openclaw.json and writes the plugin into these sections:

• plugins.allow
• plugins.load.paths
• plugins.entries.openclaw-bonree-plugin

Example:

{
  "diagnostics": {
    "enabled": true
  },
  "plugins": {
    "allow": ["openclaw-bonree-plugin"],
    "load": {
      "paths": [
        "/Users/yourname/.openclaw/extensions/openclaw-bonree-plugin"
      ]
    },
    "entries": {
      "openclaw-bonree-plugin": {
        "enabled": true,
        "config": {
          "endpoint": "https://oneupload.bonree.com/APM/otel",
          "headers": {
            "x-br-acid": "your-accountGUID",
            "x-br-envid": "your-env-id",
            "x-br-attrs": "datacenter=1"
          },
          "serviceName": "openclaw-agent"
        }
      }
    }
  }
}

Verify Installation

Run the following command after deployment:

openclaw plugins list

If the installation is successful, the list should include openclaw-bonree-plugin and show it in a loaded or enabled state.

You can also check whether the gateway restart succeeded:

openclaw gateway restart

If the restart still fails, run:

openclaw doctor

Uninstall

Standard uninstall:

curl -fsSL https://one.bonree.com/docs/en/en/openclaw/uninstall.sh | bash

Skip confirmation:

curl -fsSL https://one.bonree.com/docs/en/en/openclaw/uninstall.sh | bash -s -- --yes

Download link:

• uninstall.sh

If you used a custom path, note the difference from the install script:

• install.sh --install-dir expects the OpenClaw state root.
• uninstall.sh --install-dir expects the actual plugin directory.

Example:

curl -fsSL https://one.bonree.com/docs/en/en/openclaw/uninstall.sh | bash -s -- \
--install-dir /path/to/extensions/openclaw-bonree-plugin

The uninstall script removes the plugin registration from openclaw.json, deletes the plugin directory, and then restarts the OpenClaw gateway.

Common Issues

• If the script reports OpenClaw CLI not found, install OpenClaw and make sure openclaw is in PATH.
• If the script reports Endpoint is unreachable, verify the endpoint address and host network connectivity first.