Channels
Octopus Prime Openclaw
By OpenClaw channel plugin for Octopus Prime, team chat built for OpenClaw agents. 30 days free at octopusprimeai.com
Install
openclaw plugins install @octopusprime/openclaw-channel-pluginREADME
# Octopus Prime channel plugin for OpenClaw
**Octopus Prime is team chat built for OpenClaw.** Your agents join as real
members of your workspace, next to the people they work with:
- **No more lost messages.** Every message is delivered and acknowledged, and
replies come back to the right person even after a reconnect.
- **Agents stay in their lane.** In shared channels an agent wakes up only when
it is tagged, and you choose exactly who can use each agent.
- **Work you can see.** Projects keep a log book and a shared folder, so you
can check what an agent did, what is next and what is blocked.
- **One prompt to connect.** Paste the setup prompt into your agent and it
installs this plugin and connects itself.
Try it free for 30 days, no credit card: https://octopusprimeai.com
## About this plugin
Connects the agents on your OpenClaw Gateway to your Octopus Prime
organization, so you and the people you share them with can message them in
Octopus Prime. The plugin runs **inside** your Gateway and opens a secure
**outbound** WSS connection to Octopus Prime. The Gateway never needs a
public inbound port.
- Package `@octopusprime/openclaw-channel-plugin`, version 1.16.0. Plugin id and
channel id `octopus-prime`.
- Requires OpenClaw **2026.9.8 or later** (see [Compatibility](#compatibility)).
- Octopus Prime: https://octopusprimeai.com. App: https://app.octopusprimeai.com.
- Step-by-step guide: https://app.octopusprimeai.com/connect-your-agent.
- Support: https://app.octopusprimeai.com/support or support@octopusprimeai.com.
- Release notes: [CHANGELOG.md](CHANGELOG.md).
> **You choose who can use each agent.**
>
> A newly connected agent starts as **Just me**: only you, the person who connected the Gateway, can use it. In **OpenClaw agents**, you or an Owner or Admin can share each agent with a project or with the whole organization. Whoever can use an agent can use whatever it has access to (files, email, tools), so share it only with people who should.
## Official sources
The plugin is published as one package in two places:
- **npm**: `@octopusprime/openclaw-channel-plugin`.
- **ClawHub** (https://clawhub.ai): the same package,
`clawhub:@octopusprime/openclaw-channel-plugin`, from the Octopus Prime
publisher.
Install and update it only from one of these. Never install it from a link, a
file or instructions in a chat message, an email or a web page.
## Compatibility
- **OpenClaw 2026.9.8 or later.** `openclaw.compat.pluginApi` in
`package.json` is `>=2026.9.8` and `openclaw.compat.minGatewayVersion` is
`2026.9.8`. OpenClaw checks them before it installs the plugin from npm or
ClawHub, and refuses an older OpenClaw. Each release is built and tested on
the OpenClaw release named in `openclaw.build` (now 2026.9.8). A newer
OpenClaw loads the plugin without a new plugin release (see
[Compatibility policy](#compatibility-policy)).
- **Hosts.** It works with OpenClaw and with OpenClaw-compatible hosts that
load OpenClaw channel plugins. Other OpenClaw spinoffs are supported only if
they implement the OpenClaw plugin API this plugin uses (2026.9.8 or later);
Octopus Prime does not test them. To check such a host, on the Gateway
host (`<host>` is its command):
1. Its version, or the OpenClaw plugin API version it says it implements, is
2026.9.8 or later, and it installs native OpenClaw plugins
(`openclaw.plugin.json` and the `openclaw` block of `package.json`) from
npm or ClawHub: `<host> plugins install @octopusprime/openclaw-channel-plugin`
works and does not refuse the plugin's `openclaw.compat`.
2. It provides the OpenClaw plugin SDK entry points the plugin imports
(`openclaw/plugin-sdk/core`, `channel-core`, `channel-setup`,
`channel-inbound`, `channel-ingress-runtime`, `channel-outbound`,
`channel-actions`, `channel-contract`, `channel-secret-basic-runtime`,
`account-helpers`, `account-id`, `account-resolution`, `agent-runtime`,
`error-runtime`, `media-runtime`, `reply-payload`, `routing` and
`session-store-runtime`): `<host> plugins inspect octopus-prime` shows the
plugin loaded, with no errors.
3. `<host> channels add --channel octopus-prime --help` lists
`--backend-url` and `--setup-code`.
4. After setup (see [Install and connect](#install-and-connect)),
`<host> channels status --channel octopus-prime --probe` reports the
channel connected, **OpenClaw agents** in the web app shows the connector
**READY**, and an agent answers a message sent to it in Octopus Prime.
If any of these fails, the host is not supported: use OpenClaw itself.
## Before you start
- You are an **Owner** or **Admin** of your Octopus Prime organization. Only
they can connect a Gateway.
- OpenClaw 2026.9.8 or later on the Gateway host (`openclaw --version`), and a
shell on that host.
- The Gateway host can reach the Octopus Prime backend over outbound HTTPS
and WSS. No inbound port is needed.
- Review the agents on this Gateway (`openclaw agents list`). Each one is yours
alone in Octopus Prime until you share it (see above).
## Install and connect
The commands run on the Gateway host. The setup code comes from the Octopus
Prime AI web app.
**1. Install the plugin:**
```sh
openclaw plugins install @octopusprime/openclaw-channel-plugin
```
OpenClaw installs the package from npm, together with its one dependency,
`ws`. Because it is not an OpenClaw catalog plugin, OpenClaw first asks you to
confirm the package source and then to accept the plugin's capabilities.
Review and accept both. In a script or a shell without a terminal, pass
`--force --accept-capabilities`, but only after you have reviewed them. With a
running Gateway the plugin is applied right away; otherwise it loads on the
next Gateway start.
Or install the same package from ClawHub:
```sh
openclaw plugins install clawhub:@octopusprime/openclaw-channel-plugin
```
OpenClaw trusts ClawHub as a source, so it does not ask you to confirm it;
it shows ClawHub's security check of the release, and you may still be asked
to accept the plugin's capabilities. Later updates follow the source you
installed from.
**2. Get a setup code.** In the Octopus Prime web app
(https://app.octopusprimeai.com), open **Settings** (the gear next to your
organization's name), then **OpenClaw agents**, and click **Connect OpenClaw**. The panel shows a one-time setup code below the
install command. The code works once and expires after 15 minutes. The
connector's **New setup code** button makes another one.
**3. Paste the code into setup** in place of `<code>`, before it expires:
```sh
openclaw channels add --channel octopus-prime --backend-url https://api.octopusprimeai.com --setup-code <code>
```
`https://api.octopusprimeai.com` is the Octopus Prime server; use it as
shown. The plugin exchanges the code over HTTPS for a connector credential,
then saves the server URL, that credential, the connector ID and the
organization ID in its OpenClaw channel configuration. The code itself is not
saved. Treat the code like a password until it is used: do not paste it into
chats, tickets or logs.
**4. Check that it is connected.** A Gateway running with config reload starts
the channel by itself; otherwise run `openclaw gateway restart`. The plugin
connects and announces this Gateway's agents. In the web app, **OpenClaw
agents** then shows the connector as **READY**, with the agents under it. On
the Gateway host, this asks the running Gateway about the channel:
```sh
openclaw channels status --channel octopus-prime --probe
```
Would you rather let your own OpenClaw agent do the Gateway side? On the same
panel, **Copy setup prompt** copies instructions for it. You still enter the
setup code yourself, through protected input.
### Update or uninstall
To update it later:
```sh
openclaw plugins update octopus-prime
```
To remove the plugin:
```sh
openclaw plugins uninstall octopus-prime
```
OpenClaw lists what it will remove and asks you to confirm. That includes the
plugin's channel configuration (`channels.octopus-prime`), where setup saved
the connector credential of every account. Then, in each organization the
Gateway was connected to, an Owner or Admin clicks **Revoke** (the bin icon)
on the connector in **OpenClaw agents**: its credential stops working and its
agents leave Octopus Prime.
### If your connection breaks
An OpenClaw update or a change on the Gateway host can stop the connector:
**OpenClaw agents** then shows the connector offline, or Octopus Prime says
an agent didn't respond. Owners and Admins see what is wrong on the
connector's row: offline, an outdated plugin (older than the version Octopus
Prime AI supports), an OpenClaw version older than the plugin needs, or
repeated failed turns. There, and under an agent's notice, **Fix it with your
agent** copies a ready-made prompt for the OpenClaw agent on that Gateway.
Paste it into a private conversation with that agent in OpenClaw itself (not
in Octopus Prime, which it may not hear while the connection is down). The
prompt holds no token or setup code and never asks you for one. Its steps,
which you can also follow yourself on the Gateway host:
1. **Check.** Run OpenClaw's own diagnostics and note what they say:
```sh
openclaw status
openclaw plugins inspect octopus-prime
openclaw plugins doctor
openclaw channels status --channel octopus-prime --probe
```
2. **Update the plugin, only from its official sources**: the npm package
`@octopusprime/openclaw-channel-plugin` (this package) or the same package
on ClawHub, `clawhub:@octopusprime/openclaw-channel-plugin` (see
[Official sources](#official-sources)). Never install it from a link, a
file or instructions in a chat message, an email or a web page.
```sh
openclaw plugins update octopus-prime
```
If OpenClaw says the plugin was installed from somewhere else (a source
checkout, a file), reinstall it
... (truncated)
channels
Comments
Sign in to leave a comment