OpenClaw 2026.4.24 status regression

Summary

OpenClaw was upgraded successfully from 2026.4.15 to 2026.4.24, and live Telegram operations remained healthy after upgrade. However, the plain text openclaw status command fails in 2026.4.24 with a qqbot plugin bootstrap error even though qqbot is not configured in the live openclaw.json.

Environment

• Host: Windows
• Installed OpenClaw version: 2026.4.24
• Previous version: 2026.4.15
• Active channels in config: Telegram only
• Active auth: OpenAI + OpenAI Codex
• Workspace: C:\Users\Dan\.openclaw\workspace

Verified facts

• openclaw --version works and reports 2026.4.24
• openclaw health is healthy
• openclaw channels list shows only Telegram configured
• openclaw channels status --deep is healthy
• openclaw status --json works
• plain openclaw status fails
• openclaw doctor runs successfully
• openclaw doctor --fix successfully archived orphan session transcripts but did not resolve the text status failure
• openclaw.json does not contain a live channels.qqbot configuration
• no QQBOT_* environment variables were found during inspection

Failing command

openclaw status

Error signature

[openclaw] Failed to start CLI: Error: PlatformAdapter not registered. Call registerPlatformAdapter() during bootstrap.
    at getPlatformAdapter (...\dist\extensions\qqbot\adapter-*.js)
    at resolveQQBotAccount (...\dist\extensions\qqbot\config-*.js)
    at Object.resolveAccount (...\dist\extensions\qqbot\config-schema-*.js)
    at resolveInspectedChannelAccount (...\openclaw\dist\account-inspection-*.js)
    at async buildChannelSummary (...\openclaw\dist\channel-summary-*.js)
    at async getStatusSummary (...\openclaw\dist\status.summary-*.js)

Diagnostic interpretation

This appears to be a path-specific regression in the human-readable openclaw status summary flow. The text status path attempts to inspect qqbot account details and hits a platform adapter bootstrap failure. This does not appear to reflect a live channel outage or a real qqbot configuration issue.

Non-fixes already tested

• Confirmed qqbot is not configured in openclaw.json
• Confirmed no QQBOT_* environment variables were set
• Ran openclaw doctor
• Ran openclaw doctor --fix
• Archived orphan session transcript files
• Tested after cleanup, same failure remained
• Temporarily renamed the openclaw-unknown-* plugin runtime deps folder; OpenClaw recreated it and the same failure returned

Current workaround

Use these commands instead of plain openclaw status:

• openclaw health
• openclaw channels status --deep
• openclaw status --json

Avoid relying on:

• openclaw status

Operational impact

• Live Telegram operations: healthy
• Admin/status hygiene: degraded in the text status path
• Severity: moderate maintenance/debugging nuisance, not current production outage

Recommendation

Treat this as a known 2026.4.24 regression until a newer OpenClaw release fixes the status path or an upstream patch is identified.