Twitch

Twitch chat support via IRC connection. OpenClaw connects as a Twitch user (bot account) to receive and send messages in channels.

Bundled plugin

If you are on an older build or a custom install that excludes Twitch, install the npm package directly:

openclaw plugins install @openclaw/twitch

openclaw plugins install ./path/to/local/twitch-plugin

Use the bare package to follow the current official release tag. Pin an exact version only when you need a reproducible install.

Details: Plugins

Quick setup (beginner)

Minimal config:

{  channels: {    twitch: {      enabled: true,      username: "openclaw", // Bot's Twitch account      accessToken: "oauth:abc123...", // OAuth Access Token (or use OPENCLAW_TWITCH_ACCESS_TOKEN env var)      clientId: "xyz789...", // Client ID from Token Generator      channel: "vevisk", // Which Twitch channel's chat to join (required)      allowFrom: ["123456789"], // (recommended) Your Twitch user ID only - get it from https://www.streamweasels.com/tools/convert-twitch-username-to-user-id/    },  },}

What it is

• A Twitch channel owned by the Gateway.
• Deterministic routing: replies always go back to Twitch.
• Each account maps to an isolated session key agent:<agentId>:twitch:<accountName>.
• username is the bot's account (who authenticates), channel is which chat room to join.

Setup (detailed)

Generate credentials

Use Twitch Token Generator:

• Select Bot Token
• Verify scopes chat:read and chat:write are selected
• Copy the Client ID and Access Token

Configure the bot

OPENCLAW_TWITCH_ACCESS_TOKEN=oauth:abc123...

{  channels: {    twitch: {      enabled: true,      username: "openclaw",      accessToken: "oauth:abc123...",      clientId: "xyz789...",      channel: "vevisk",    },  },}

If both env and config are set, config takes precedence.

Access control (recommended)

{  channels: {    twitch: {      allowFrom: ["123456789"], // (recommended) Your Twitch user ID only    },  },}

Prefer allowFrom for a hard allowlist. Use allowedRoles instead if you want role-based access.

Available roles: "moderator", "owner", "vip", "subscriber", "all".

Token refresh (optional)

Tokens from Twitch Token Generator cannot be automatically refreshed - regenerate when expired.

For automatic token refresh, create your own Twitch application at Twitch Developer Console and add to config:

{  channels: {    twitch: {      clientSecret: "your_client_secret",      refreshToken: "your_refresh_token",    },  },}

The bot automatically refreshes tokens before expiration and logs refresh events.

Multi-account support

Use channels.twitch.accounts with per-account tokens. See Configuration for the shared pattern.

Example (one bot account in two channels):

{  channels: {    twitch: {      accounts: {        channel1: {          username: "openclaw",          accessToken: "oauth:abc123...",          clientId: "xyz789...",          channel: "vevisk",        },        channel2: {          username: "openclaw",          accessToken: "oauth:def456...",          clientId: "uvw012...",          channel: "secondchannel",        },      },    },  },}

Access control

{  channels: {    twitch: {      accounts: {        default: {          allowFrom: ["123456789", "987654321"],        },      },    },  },}

{  channels: {    twitch: {      accounts: {        default: {          allowedRoles: ["moderator", "vip"],        },      },    },  },}

{  channels: {    twitch: {      accounts: {        default: {          requireMention: false,        },      },    },  },}

Troubleshooting

First, run diagnostic commands:

openclaw doctoropenclaw channels status --probe

Using env token source for mybotAccess token refreshed for user 123456 (expires in 14400s)

Config

Account config

Provider options

• channels.twitch.enabled - Enable/disable channel startup
• channels.twitch.username - Bot username (simplified single-account config)
• channels.twitch.accessToken - OAuth access token (simplified single-account config)
• channels.twitch.clientId - Twitch Client ID (simplified single-account config)
• channels.twitch.channel - Channel to join (simplified single-account config)
• channels.twitch.accounts.<accountName> - Multi-account config (all account fields above)

Full example:

{  channels: {    twitch: {      enabled: true,      username: "openclaw",      accessToken: "oauth:abc123...",      clientId: "xyz789...",      channel: "vevisk",      clientSecret: "secret123...",      refreshToken: "refresh456...",      allowFrom: ["123456789"],      allowedRoles: ["moderator", "vip"],      accounts: {        default: {          username: "mybot",          accessToken: "oauth:abc123...",          clientId: "xyz789...",          channel: "your_channel",          enabled: true,          clientSecret: "secret123...",          refreshToken: "refresh456...",          expiresIn: 14400,          obtainmentTimestamp: 1706092800000,          allowFrom: ["123456789", "987654321"],          allowedRoles: ["moderator"],        },      },    },  },}

Tool actions

The agent can call twitch with action:

• send - Send a message to a channel

Example:

{  action: "twitch",  params: {    message: "Hello Twitch!",    to: "#mychannel",  },}

Safety and ops

• Treat tokens like passwords — Never commit tokens to git.
• Use automatic token refresh for long-running bots.
• Use user ID allowlists instead of usernames for access control.
• Monitor logs for token refresh events and connection status.
• Scope tokens minimally — Only request chat:read and chat:write.
• If stuck: Restart the gateway after confirming no other process owns the session.

Limits

• 500 characters per message (auto-chunked at word boundaries).
• Markdown is stripped before chunking.
• No rate limiting (uses Twitch's built-in rate limits).

Related

• Channel Routing — session routing for messages
• Channels Overview — all supported channels
• Groups — group chat behavior and mention gating
• Pairing — DM authentication and pairing flow
• Security — access model and hardening