OpenClaw

Easy setup

inline agents setup --target openclaw

The command checks the installed OpenClaw version before creating a bot, installs the matching trusted plugin, restarts the gateway, and only reports ready after a live Inline probe. If it stops, the error includes the failed phase and retry command; no failed or partial run is reported as ready.

Install

Install the compatible plugin for the current OpenClaw line:

openclaw plugins install @inline-openclaw/inline --force --accept-capabilities

Version Match

Install a matched version with:

openclaw plugins install @inline-openclaw/inline --force --accept-capabilities

On OpenClaw 2026.8, --accept-capabilities approves the capabilities declared by Inline's trusted first-party package so the noninteractive install cannot stall on a prompt. Older supported hosts do not recognize that flag; install their matched 0.0.63 package with --force only.

Configure

Set channels.inline:

channels:
  inline:
    enabled: true
    token: "<INLINE_BOT_TOKEN>"

You may omit token and provide INLINE_TOKEN to the gateway.

Defaults:

• dmPolicy: "pairing"
• groupPolicy: "open"
• requireMention: true

Configure allowlists for a restricted bot. A mention requirement is not an operator allowlist.

How it behaves

OpenClaw follows the same rules as Hermes in Inline.

• Only a mention, a reply to the bot, a DM, a command for it, or a thread it follows wakes it. Words never do, its name included.
• A message that starts by mentioning someone else isn't for it, and neither is a reply to someone else, unless it also mentions the bot.
• A thread's first message decides which bots follow. A bot mentioned later answers once without following. /follow and /unfollow change it, and so does asking the agent.
• Reply threads are Auto or On, per chat, DMs included. Auto answers in the chat and starts a thread when someone asks. On answers each top-level message in a reply thread. Set it with /threads, the agent settings, or by asking the agent; On is never bot-wide, so a new chat's first message doesn't get a thread.
• Answers quote only another bot that asked, so the answer reaches it. Its reply back needs no answer, so two bots can't wake each other without end.
• Messages sent while the gateway was down aren't answered after a restart.

Restart

Restart the gateway:

openclaw gateway restart

List plugins:

openclaw plugins list

Check the Inline channel:

openclaw channels status --channel inline --probe --json

Inspect the plugin:

openclaw plugins inspect inline --json

Open a DM with the bot, complete pairing, and verify it works.

Update

Ask OpenClaw to update the tracked Inline plugin:

openclaw plugins update inline --accept-capabilities

Restart after active work finishes:

openclaw gateway restart

Checks

• Plugin missing: check openclaw plugins list and the gateway's install environment.
• Token missing: set channels.inline.token or INLINE_TOKEN.
• DM ignored: complete pairing or check the sender allowlist.
• Group ignored: check group policy, sender policy, and the mention. A thread the bot only wrote in isn't one it follows; use /follow.
• No reply: check provider sign-in and gateway errors.

Plugin source and configuration

Source

• Plugin source and configuration