[Bug]: Multiple regressions in 2026.4.8 - Gateway high CPU, CLI timeout, Discord voice broken, Messenger bot broken

Summary

After upgrading from OpenClaw 2026.4.1 to 2026.4.8, multiple critical features stopped working:

1. Gateway CPU usage spikes to 80%+ (normally ~5%)
2. openclaw agent CLI commands timeout after 32 seconds
3. Discord voice channel join fails with "The operation was aborted"
4. Facebook Messenger bot stops responding - only default fallback messages sent

Rollback to 2026.4.1 fixes all issues.

Environment

• OpenClaw version: 2026.4.8 (regression from 2026.4.1)
• OS: Ubuntu 24.04 LTS (AWS EC2 t3.small)
• Node.js: v25.4.0
• Gateway: Local mode (ws://127.0.0.1:18789)

Regression Details

1. Gateway High CPU Usage

2026.4.1: Gateway CPU usage ~5% normal operation
2026.4.8: Gateway CPU usage 80-90% continuously

# 2026.4.8 - Gateway consuming 81.8% CPU
ubuntu    752113 81.8 34.6 10637520 676412 ?     Rsl  12:58   6:33 openclaw-gateway

2. CLI Agent Commands Timeout

2026.4.1: openclaw agent --agent public --message "test" --json returns in ~5-10 seconds
2026.4.8: Same command times out after 32 seconds

$ openclaw agent --agent public --message "test" --json --timeout 30
# Result: gateway timeout after 32000ms
# Gateway target: ws://127.0.0.1:18789

3. Discord Voice Channel Broken

2026.4.1: /vc join works correctly - bot joins and stays in channel
2026.4.8: Bot joins channel then immediately leaves with error:

DiscordAPIError[10062]: Unknown interaction
{
  "name": "DiscordAPIError[10062]",
  "code": "The operation was aborted",
  "stack": "AbortError: The operation was aborted\n    at EventTarget.abortListener (node:internal/deps/undici/undici:..."
}

4. Facebook Messenger Bot Broken

Architecture:

• Facebook Webhook (PHP on hungaryvfr.hu) → Cloudflare Tunnel → fb_bridge.js (port 18082) → OpenClaw agent

2026.4.1: Full flow works - user message → OpenClaw generates reply → reply sent to Messenger
2026.4.8:

• User messages still reach OpenClaw (session created)
• OpenClaw generates reply (visible in session history)
• Reply never reaches fb_bridge.js - only default fallback message sent
• Root cause: openclaw agent CLI timeout prevents reply retrieval

// fb_bridge.js tries to get reply via CLI:
const { stdout } = await execFileAsync('/home/ubuntu/.npm-global/bin/openclaw', [
  'agent', '--agent', agentId, '--message', prompt, '--json', '--timeout', '90'
]);

// 2026.4.8: This times out, so fallback message is used:
reply = `Szia! 👋 Köszi az üzeneted — hamarosan részletesebben válaszolok.`;

Steps to Reproduce

Gateway CPU Issue

# 1. Upgrade to 2026.4.8
openclaw update

# 2. Restart gateway
openclaw gateway restart

# 3. Monitor CPU
watch -n 1 'ps aux | grep openclaw-gateway | grep -v grep'
# Observe: CPU usage climbs to 80%+ within minutes

CLI Timeout Issue

# Test CLI agent command
openclaw agent --agent public --message "Hello test" --json --timeout 30

# 2026.4.1: Returns JSON response in ~5-10 seconds
# 2026.4.8: Times out after 32 seconds with "gateway timeout"

Discord Voice Issue

# In Discord channel with OpenClaw bot:
/vc join

# 2026.4.1: Bot joins and stays
# 2026.4.8: Bot joins then immediately leaves with "The operation was aborted"

Messenger Bot Issue

# 1. Set up Facebook Messenger integration via fb_bridge.js
# 2. Send message to Messenger bot
# 3. Check fb_bridge logs

# 2026.4.1: Generated reply returned to user
# 2026.4.8: Only default fallback message returned

Workaround

Rollback to 2026.4.1 fixes all issues:

# Downgrade (example using npm)
npm install -g [email protected]
openclaw gateway restart

Related Issues

Possibly related to other 4.x regressions:

• #63098 (Discord voice issue already reported)
• Similar pattern to "Regression (worked in v4.1, broken in v4.2)" issues

Additional Context

• Gateway is running in local mode (not remote)
• No changes to configuration between 4.1 → 4.8
• Cloudflare tunnel and fb_bridge.js are working correctly (verified independently)
• The issue appears to be in the gateway daemon itself, not the CLI or integrations

Diagnostic Data

Gateway Status (2026.4.8)

{
  "runtime": "running",
  "rpcProbe": "timeout",
  "cpuUsage": "81.8%",
  "memoryUsage": "676MB"
}

Session List (2026.4.8)

Sessions are created but CLI cannot retrieve replies due to timeout.

Priority: High - Multiple critical features broken in 4.8, affecting production usage.