Channel cleanup becomes messy when you do not decide whether you are disabling or deleting. OpenClaw supports both, and they solve different problems.
Quick answer
Disable a channel when you want a quick stop. Remove a channel when you want to delete the connection details and stop the runtime from trying to use it again.
Command line steps
1. List the current channel state
Start by seeing what is actually configured.
BASH
$openclaw channels list
openclaw channels status --probe
2. Disable the channel when you want a reversible pause
This keeps the config around but stops the runtime from starting that channel.
BASH
$openclaw config set channels.telegram.enabled false
# or, for WhatsApp:
openclaw config set channels.whatsapp.enabled false
3. Remove the channel when you want a clean delete
Use the dedicated remove command for full cleanup.
BASH
$openclaw channels remove --channel telegram --delete
# or:
openclaw channels remove --channel whatsapp --delete
openclaw gateway restart
What to check if it still fails
- If the channel still appears active after removal, restart the gateway and check the probe again.
- If you only needed to stop traffic temporarily, prefer disable over delete so you can roll back quickly.
- If group replies are the real problem, debug policy and allowlists before you remove the whole channel.