Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Bug: Discord & Zalo channels removed after upgrade to 2026.5.2 — no migration path

Summary

Upgrading from a previous OpenClaw version to 2026.5.2 silently drops Discord and Zalo channel support. Both channels were fully functional before the upgrade with existing bot tokens, allowlists, and guild configs. After upgrade, openclaw status shows only Telegram. Discord and Zalo are completely absent from the channels table.

Impact

• Severity: High — Production bots stop working. Users relying on Discord/Zalo for daily workflows lose all bot access with no warning or migration path.
• Affects any user who had Discord or Zalo configured in channels.discord / channels.zalo before upgrading.

Environment

• OpenClaw version: 2026.5.2 (8b2a6e5)
• OS: macOS 26.3.1 (arm64), Node 22.22.0
• Previous version: had Discord + Zalo working as built-in channels
• Install method: npm global (pnpm)

What happened

1. Discord and Zalo were working as built-in channels in the previous version.
2. Upgraded to 2026.5.2.
3. openclaw doctor reports:

   plugins.allow: plugin not found: discord (stale config entry ignored)
   plugins.allow: plugin not found: zalo (stale config entry ignored)

4. openclaw status → only Telegram channel listed. Discord and Zalo gone.
5. openclaw plugins install clawhub:@openclaw/discord → ClawHub package "@openclaw/discord" has no installable version.
6. openclaw plugins install clawhub:@openclaw/zalo → ClawHub package "@openclaw/zalo" has no installable version.

Evidence

Config still has channel definitions (not deleted)

// channels.discord
{
  "allowFrom": ["xxxxx2883689xxxxxx"],
  "dmPolicy": "allowlist",
  "enabled": true,
  "groupPolicy": "allowlist",
  "guilds": {
    "1492927042818408762": {
      "requireMention": false,
      "users": ["xxxxx2883689xxxxxx"]
    }
  },
  "token": { "id": "DISCORD_BOT_TOKEN", "provider": "default", "source": "env" }
}

// channels.zalo
{
  "enabled": true,
  "accounts": {
    "office": {
      "botToken": "xxxx55…zAXO",
      "name": "office-super-assistant",
      "enabled": true,
      "dmPolicy": "pairing",
      "groupPolicy": "disabled"
    }
  }
}

Dist still has Discord/Zalo JS bundles

dist/discord-Cv2PBeIv.js
dist/zalo-js-mqG910Cp.js
dist/plugin-sdk/discord.js
dist/plugin-sdk/zalouser.js

But no extension directory for either

ls dist/extensions/ → no "discord" or "zalo" directory

All other channels (telegram, signal, slack, matrix, irc…) have extension dirs. Discord and Zalo are missing.

Stock extensions list (excerpt)

The stock: extensions include telegram, signal, slack, matrix, irc, etc. but not discord or zalo.

Root cause (likely)

• Discord and Zalo were moved from built-in to external plugin (@openclaw/discord, @openclaw/zalo on ClawHub).
• But the ClawHub packages have no installable version published.
• The built-in extension directories were removed from dist/extensions/ but the JS bundles remain orphaned in dist/.
• No migration/upgrade script preserves the channels during the transition.

Expected behavior

One of:

1. Built-in fallback: If the plugin isn't installed, fall back to the built-in channel support (code still exists in dist).
2. Auto-install: openclaw doctor --fix should auto-install the Discord/Zalo plugins during upgrade.
3. Publish the plugins: Make @openclaw/discord and @openclaw/zalo installable on ClawHub before removing built-in support.
4. Upgrade guard: If channels are configured but the required plugin is unavailable, warn explicitly and refuse to drop the channel rather than silently removing it.

Workaround

None found. Config is present, plugin is unavailable, built-in code is orphaned.

Suggested fix

• Immediate: Publish @openclaw/discord and @openclaw/zalo to ClawHub with installable versions, OR restore the built-in extension directories in the next patch release.
• Long-term: Add upgrade migration that checks for configured channels whose plugins are missing and either auto-installs or preserves backward-compatible built-in support.

Steps to reproduce

Start OpenClaw 2026.5.2 with Zalo and Discord

Expected behavior

Before OpenClaw 2026.5.2, Zalo and Discord still working

Actual behavior

Zalo and Discord not working

OpenClaw version

2026.5.2

Operating system

macOS 26.3.1 (arm64)

Install method

npm global

Model

minimax 2.7

Provider / routing chain

OpenClaw --> minimax

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response