Bug type

Regression (worked before, now fails)

Summary

Three related dashboard UI issues on 2026.2.26:

1. Channels page: Accounts and Capabilities sections show Unsupported schema node. Use Raw mode. in Form mode for Telegram config
2. Usage page: Opens with 0 data / empty charts. Requires manual Refresh click to populate.
3. Debug page: Telegram health shows "running": false while Channels page shows Running: Yes and messages deliver successfully. Stale/contradictory health state.

Steps to reproduce

1. Open dashboard at http://localhost:58789
2. Navigate to Channels → Telegram section → scroll to Accounts → red error banner
3. Navigate to Usage → page loads with 0 data, 0 tokens, no charts
4. Navigate to Debug → Health section → Telegram shows running: false despite active bot

Expected behavior

1. Channels: Accounts and Capabilities render as editable form fields
2. Usage: Page auto-loads data on visit without requiring manual Refresh
3. Health: Telegram running state is consistent across Channels page and Debug health endpoint

Actual behavior

1. Red error banners on Channels page for Accounts and Capabilities sections
2. Usage page shows empty state (0 tokens, no timeline data, no sessions) until Refresh is clicked
3. Debug health JSON shows "running": false for Telegram while bot is actively polling and delivering messages

OpenClaw version

2026.2.26

Operating system

macOS 26.3 (arm64)

Install method

npm global

Logs, screenshots, and evidence

Impact and severity

Affected: All dashboard users on 2026.2.26
Severity: Low (cosmetic/UX, no functional impact)
Frequency: 100% repro on all three
Consequence: Channels config sections can't be edited in Form mode (must use Raw), Usage requires extra click, Health state is misleading

Additional information

Gateway is loopback-only on port 58789. Telegram channel is configured via polling mode. Bot token is set via config. All messaging works correctly despite the dashboard UI issues.

For issue #3, the Debug health endpoint returns "running": false and "lastStartAt": null for Telegram, but the Channels page probe returns ok and messages send/deliver successfully.