openclaw - 💡(How to fix) Fix [Bug]: Twitch channel enabled but never connects after update (schema/config mismatch, no clear validation path) [1 participants]

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Summary

After updating OpenClaw, Twitch channel shows as enabled but never successfully connects. Status reports: “Account has never connected successfully.”

Environment

• OpenClaw version: 2026.4.1 (upgraded via npm global install) • Host: Linux (Raspberry Pi) • Gateway managed via openclaw gateway commands • Twitch plugin appears bundled/enabled

What we expected

Twitch channel should connect and join chat once valid credentials are present.

What happened

• Twitch remains in WARN/unconnected state • We hit config schema friction while trying multiple config formats • OpenCLAW onboard did not expose a clear Twitch path in this environment • This created a chicken-and-egg flow where config discovery is hard without a successful load path

Repro (high-level)

1. Upgrade OpenClaw to the latest (npm install -g openclaw@latest)
2. Configure Twitch credentials in env
3. Enable Twitch channel in config
4. Restart gateway
5. Run openclaw status --deep
6. Observe Twitch WARN: account has never connected successfully • Tried both flat config and accounts.default config shape • Tried fresh tokens • Bot account was a moderator in the channel • Channel/account names verified correct

Notes

• Credentials were rotated/refreshed during testing • Bot account is a moderator in the target channel • We intentionally redacted channel/account identifiers for security

Requested improvements

1. Clear canonical Twitch config schema example for current release
2. Better validation errors (show exact invalid path + expected shape)
3. OpenCLAW onboard parity for Twitch setup in all supported environments
4. A dry-run config validation command that includes channel/plugin schema checks before restart
5. Connection diagnostics section for Twitch (auth, scopes, channel join, rate limits)

Impact

This blocks a production-safe Twitch rollout and increases the risk of restarts while troubleshooting config shape issues.

Steps to reproduce

1. Install/update to OpenClaw 2026.4.2
2. Configure Twitch channel with a valid bot username, client ID, access token, target channel, and allowlist
3. Restart gateway
4. Run openclaw status --deep
5. Observe Twitch shows ON / WARN with “Account has never connected successfully.”
6. Check logs and observe pattern: • Connected to Twitch as <bot> • immediate auto-restart attempt 1/10 in 5s • repeats until retry limit

Expected behavior

With valid Twitch credentials and a correct channel config, the Twitch channel should connect successfully, remain connected, join chat, and show as healthy in openclaw status --deep instead of entering an auto-restart loop.

Actual behavior

The Twitch plugin appears to authenticate and log Connected to Twitch as <bot>, but immediately enters the health-monitor auto-restart loop. In openclaw status --deep, Twitch shows ON / WARN with Account has never connected successfully, and the connection never stabilizes.

OpenClaw version

OpenClaw 2026.4.2

Operating system

Linux 6.12.75+rpt-rpi-2712 (arm64) on Raspberry Pi 5, Node.js 24.13.0

Install method

No response

Model

claude-opus-4-6; gpt-5.4

Provider / routing chain

• Channel: Twitch (via @openclaw/twitch bundled plugin) • Auth: StaticAuthProvider (no clientSecret / no token refresh) • Token source: env var (${TWITCH_ACCESS_TOKEN}) • Config shape: channels.twitch.accounts.default • Gateway: self-hosted, systemd, loopback bind • Health monitor: triggers auto-restart loop immediately after IRC connect • Fallback: none — retries until 10/10 attempts exhausted, then stops

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response