Description

Telegram is correctly configured in config.json and nullclaw config show displays it correctly, but nullclaw channel list always shows "Telegram: not configured" and nullclaw channel start telegram says "No messaging channel configured". Tested on both v2026.4.17 releases (before and after #858).

Expected behavior

nullclaw channel list should show "Telegram: configured" and nullclaw channel start telegram should start polling.

Steps to reproduce

nullclaw onboard --provider groq --api-key ...
Add to ~/.nullclaw/config.json:

json{
"channels": {
"cli": true,
"telegram": {
"accounts": {
"main": {
"bot_token": "TOKEN",
"allow_from": [123456789]
}
}
}
}
}

nullclaw config show | grep telegram → config is there ✓
nullclaw channel list → Telegram: not configured ✗
nullclaw channel start telegram → "No messaging channel configured" ✗

Version

v2026.4.17.

OS

Other