Summary

During OpenClaw setup, an invalid channels.telegram.groups shape caused gateway startup/config failure with a low-level schema message rather than a guided migration or actionable config repair hint.

The observed error was:

channels.telegram.groups: invalid config: must be object

The setup was recovered after manually fixing the config shape, but the failure mode was confusing during onboarding/debugging.

Environment

• OpenClaw: observed during May 2026 setup; current install later upgraded to 2026.5.12
• Channel: Telegram
• Context: configuring Telegram group/forum topic routing and per-topic agent mapping

Observed behavior

1. Gateway config contained an invalid channels.telegram.groups shape.
2. OpenClaw failed startup/config validation with:

channels.telegram.groups: invalid config: must be object

3. The operator had to manually inspect/repair the config shape.
4. The error did not clearly explain the expected nested Telegram group/topic schema or suggest a migration/fix command.

Expected behavior

When channels.telegram.groups has the wrong shape, OpenClaw should provide a more actionable error, for example:

• show the expected schema shape for Telegram groups/topics,
• identify which group key is malformed,
• suggest running a config migration/doctor fix if applicable, or
• keep enough diagnostics in startup logs to avoid a silent/channel-down setup experience.

Why this matters

Telegram group/forum-topic routing is a common setup path, and the config is nested enough that shape mistakes are easy. A schema-only error is technically correct but not very recoverable for onboarding.

Notes

This is distinct from the already-opened Telegram runtime issues around forum-topic voice notes and usage footers. This issue is about config validation/startup UX for invalid Telegram group config shape.