OpenClaw Bot Not Working? Here's How to Diagnose and Fix It

There isn't enough evidence to nail down the exact failure of your OpenClaw botchat just yet, but the correct diagnostic path is well-established: you need to run

openclaw status

openclaw gateway status

openclaw logs --follow

openclaw doctor

openclaw channels status --probe

What to Check Right Away

• A healthy baseline should show:

  Runtime: running

  ,

  Connectivity probe: ok

  , a valid Capability, and a channel probe that reports the transport is connected. Where supported, you should also see works or

  audit ok

  .
• If your Telegram bot is "online but the group is silent," the documentation points to checking requireMention and the bot's privacy mode. For the bot to see all group messages, you must disable privacy mode via /setprivacy with BotFather, or add the bot as a group administrator. Crucially, after making this change, you must remove and re-add the bot to the group for Telegram to apply the new settings.
• If you see a network error when sending messages, the right path is to check the Telegram API logs and fix DNS/IPv6/proxy routing to api.telegram.org.
• If startup reports a

  getMe returned 401

  error, the token from BotFather is invalid or has expired. You'll need to update the botToken, tokenFile, or TELEGRAM_BOT_TOKEN for the default account.
• If polling stalls or reconnects are slow, you must monitor

  openclaw logs --follow

  . If the problem persists, the documentation suggests the root cause often circles back to proxy, DNS, or IPv6 misconfiguration.
• If you encounter a getUpdates 409 conflict, it means another OpenClaw gateway, script, or external poller is using the same bot token. OpenClaw's Telegram architecture is designed so that only one active long-polling instance should use a single bot token at a time.

If the Bot Broke After an Update

• After an update, the documentation recommends running

  openclaw status --all

  , then

  openclaw doctor --fix

  , followed by

  openclaw gateway restart

  , and finally verifying with

  openclaw status --all

  again.
• If you see

  plugin load failed: dependency tree corrupted

  , it means a channel is configured, but the plugin failed to load due to a corrupt dependency tree. The

  openclaw doctor --fix

  command is the one specified by the docs to clear old staging and authorization shadows before restarting the gateway.

What a Correct Telegram Setup Looks Like

• OpenClaw's Telegram integration does not use

  openclaw channels login telegram

  . Instead, it reads the token from your configuration or environment variables, requires

  channels.telegram.enabled: true

  , and then starts the gateway.
• Direct messages use a pairing system by default. After starting the gateway, you need to run

  openclaw pairing list telegram

  and approve the pairing, if necessary.

The Short Version

• For now, I cannot definitively say “it broke because of X” based on the available information. The evidence is insufficient.
• However, to properly fix the issue, you must first gather the output from the five diagnostic commands listed above. For Telegram specifically, the four most suspect areas are: privacy/mention settings, a 401 token error, DNS/IPv6/proxy problems, or a 409 polling conflict.