Applies to: Octopus Prime channel plugin 1.1.0 · OpenClaw ≥ 2026.9.8 · Last verified: 2026-10-10

Full index: /ai/llms.txt · Markdown: append .md to any /ai/ URL

# Compatibility

## Requirements

| Item | Requirement | How it is enforced |
|---|---|---|
| OpenClaw | **2026.9.8 or newer** (a floor; no upper bound is declared) | The plugin package declares `openclaw.compat.pluginApi` `>=2026.9.8`. OpenClaw checks this field before installing a non-bundled plugin (OpenClaw docs: plugins/manifest/package-json, cli/plugins/install); on an older OpenClaw the install fails and asks you to upgrade OpenClaw or choose a compatible version. `peerDependencies.openclaw` `>=2026.9.8` is also declared but is package metadata only. |
| Node | What OpenClaw requires: **Node 24.16+ or Node 26.1+** (Node 22, 23 and 25 are not supported by OpenClaw) | OpenClaw's own runtime requirement (OpenClaw docs: install/node). The plugin declares no separate `engines` field; it uses Node's built-in `node:sqlite` module for its local queue. Plugin 1.1.0 was built and tested with Node 24.19.0. |
| Protocol token | `2026.9.7` | Sent during setup and negotiated on every connect. The service accepts only `2026.9.7`: otherwise setup fails with HTTP 426 `Unsupported OpenClaw plugin API <v>. Supported: ['2026.9.7']`, and a running connection is closed with code 4426 and the connector shows `INCOMPATIBLE`. |
| OpenClaw account | `default` only | Setup refuses other accounts (`Octopus Prime supports the default connector account only`). |
| Network | Outbound HTTPS and WSS to `api.octopusprimeai.com` | No inbound port is used. |
| Install source | Plugin archive provided by Octopus Prime, installed with `openclaw plugins install <plugin package>` | The OpenClaw Control UI and the agent `plugins` tool cannot install local archives. |

## The 2026.9.7 protocol token

- `2026.9.7` is a frozen identifier of the connection protocol between the plugin and the Octopus Prime service. It is **not** your OpenClaw version and does not need to match it.
- A Gateway running OpenClaw 2026.9.8 or newer correctly shows `plugin API 2026.9.7` on its connector in the web app.
- The real OpenClaw version is sent with every heartbeat; Owners and Admins see it on the connector, and Health Watch records it in each incident.
- It changes only if the connection protocol changes; Octopus Prime would then provide a matching plugin package. A 426 or 4426 means the installed plugin build and the service disagree about this token, not that your OpenClaw version is wrong.

## Version table

| Plugin | OpenClaw minimum | OpenClaw verified | Protocol token | Node | Verified on | Notes |
|---|---|---|---|---|---|---|
| 1.1.0 | 2026.9.8 | 2026.9.8 | `2026.9.7` | 24.16+ or 26.1+ (built and tested with 24.19.0) | 2026-10-10 | Current build. Loads on OpenClaw 2026.9.8; reconnects automatically, detects dead connections and redelivers after outages without losing messages. Ships the Doctor contract so replacement installs work on OpenClaw 2026.9.8. Newer OpenClaw releases are within the declared range. |

Machine-readable: /ai/compatibility.json.

## Builds older than 1.1.0

Symptoms of an older plugin build: `prepared payload capability mismatch (thread)`, `The reply channel changed or cannot preserve its sender`, `Delivery platform claim was lost`, or `Plugin config repair could not be inspected` when replacing it on OpenClaw 2026.9.8. Fix: install 1.1.0 with `openclaw plugins install <plugin package> --force` (add `--accept-capabilities` non-interactively). Your `channels.octopus-prime` config is kept.

## Before updating OpenClaw

1. Check this page and /ai/changelog for the OpenClaw versions verified with your plugin build.
2. Note your current version: `openclaw --version`.
3. Update OpenClaw as usual (`openclaw update`; OpenClaw docs: cli/update). OpenClaw handles plugin compatibility during the update: when an installed plugin's compatibility range excludes the new core, the core update still succeeds, OpenClaw records a named notice, and that plugin can stay unavailable until a compatible version is installed (OpenClaw docs: cli/update/how-updates-run).

## After an OpenClaw update breaks the plugin

Symptoms: the `octopus-prime` channel is missing, `plugins inspect` reports an error, the connector shows `OFFLINE` or `INCOMPATIBLE`, or Health Watch opens an incident right after an update.

1. `openclaw status --all`: look for plugin load errors.
2. `openclaw plugins inspect octopus-prime --runtime --json`: `code: "sdk-incompatible"` means this plugin build does not load on the new OpenClaw.
3. `openclaw update status`: shows the update outcome and any plugin notices.
4. `openclaw doctor --fix`: repairs stale plugin config and state (OpenClaw docs: channels/troubleshooting, cli/doctor).
5. `openclaw gateway restart`.
6. `openclaw status --all` and `openclaw channels status --probe --channel octopus-prime` again.
7. Still incompatible: install the plugin package Octopus Prime provides for that OpenClaw version (`openclaw plugins install <plugin package> --force`), or return OpenClaw to a verified version with `openclaw update --tag <version>` (OpenClaw docs: cli/update), then restart and recheck.
8. Meanwhile nothing is lost on the Octopus Prime side: messages to this Gateway's agents wait as `OFFLINE` and are delivered in order after reconnect (unless they pass the 30-day window). When an OpenClaw release breaks connections for organizations, affected organizations get a notice in the app, and another when it is fixed.
9. If it still fails: `openclaw triage --non-interactive` and contact support@octopusprimeai.com (/ai/troubleshooting#escalate-to-support).