History

Merge upstream openclaw/main into ironclaw

Resolve 17 merge conflicts preserving ironclaw branding while
incorporating all upstream bug fixes and feature updates:

- Keep ironclaw name, CLI branding, and custom web app bundling
- Take upstream's new gateway auth token auto-generation
- Take upstream's shouldSkipRespawnForArgv respawn guard
- Take upstream's refactored skills frontmatter (resolveOpenClawManifestBlock)
- Merge upstream's ~/.agents/skills path + ironclaw's bundled skills watcher
- Take upstream's new GatewayToolsConfig alongside ironclaw's GatewayWebAppConfig
- Take upstream's minimalTestGateway guard in server.impl.ts
- Take upstream's refactored fs-mocked tests with ironclaw variants
- Take upstream's system message + subagent polling guidance tests
- Take upstream's dynamic import pattern in onboarding wizard
- Fix extensions/feishu workspace reference (openclaw -> ironclaw)
- Regenerate pnpm-lock.yaml with updated dependencies

Co-authored-by: Cursor <cursoragent@cursor.com>

2026-02-15 15:17:52 -08:00

src

fix: dedupe probe/token base types (#16986 ) (thanks @iyoda)

2026-02-15 11:36:54 -06:00

test

feat: Twitch Plugin (#1612 )

2026-01-26 13:48:10 -06:00

CHANGELOG.md

chore: bump version to 2026.2.15

2026-02-15 04:50:31 +01:00

index.ts

chore: Enable typescript/no-explicit-any rule.

2026-02-02 16:18:09 +09:00

openclaw.plugin.json

refactor: rename to openclaw

2026-01-30 03:16:21 +01:00

package.json

Merge upstream openclaw/main into ironclaw

2026-02-15 15:17:52 -08:00

README.md

refactor: rename to openclaw

2026-01-30 03:16:21 +01:00

README.md

@openclaw/twitch

Twitch channel plugin for OpenClaw.

Install (local checkout)

openclaw plugins install ./extensions/twitch

Install (npm)

openclaw plugins install @openclaw/twitch

Onboarding: select Twitch and confirm the install prompt to fetch the plugin automatically.

Config

Minimal config (simplified single-account):

⚠️ Important: requireMention defaults to true. Add access control (allowFrom or allowedRoles) to prevent unauthorized users from triggering the bot.

{
  channels: {
    twitch: {
      enabled: true,
      username: "openclaw",
      accessToken: "oauth:abc123...", // OAuth Access Token (add oauth: prefix)
      clientId: "xyz789...", // Client ID from Token Generator
      channel: "vevisk", // Channel to join (required)
      allowFrom: ["123456789"], // (recommended) Your Twitch user ID only (Convert your twitch username to ID at https://www.streamweasels.com/tools/convert-twitch-username-%20to-user-id/)
    },
  },
}

Access control options:

requireMention: false - Disable the default mention requirement to respond to all messages
allowFrom: ["your_user_id"] - Restrict to your Twitch user ID only (find your ID at https://www.twitchangles.com/xqc or similar)
allowedRoles: ["moderator", "vip", "subscriber"] - Restrict to specific roles

Multi-account config (advanced):

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

Setup

Create a dedicated Twitch account for the bot, then generate credentials: Twitch Token Generator
- Select Bot Token
- Verify scopes chat:read and chat:write are selected
- Copy the Access Token to token property
- Copy the Client ID to clientId property
Start the gateway

Full documentation

See https://docs.openclaw.ai/channels/twitch for:

Token refresh setup
Access control patterns
Multi-account configuration
Troubleshooting
Capabilities & limits