If the Bot Is Completely Silent

A completely unresponsive bot typically points to one of three failures:

• The gateway or runtime is not running, or its probe fails.
• The Telegram token is missing or incorrect in your config or environment.
• The Telegram plugin failed to load. A known issue reports the exact error telegram plugin not available, which means the plugin itself never initialized.

If the Bot Connects but Replies Stall

Evidence from bug reports suggests that gateway runtime problems—not token issues—are the likely culprit. One documented case shows Telegram replies stalling because the gateway enters a CPU spin state, essentially getting stuck in a processing loop.

The Correct Diagnostic Order

Follow this sequence to pinpoint the problem without chasing false leads:

1. Check gateway/runtime health first. Do not change configuration yet. Use the appropriate status commands to verify the baseline.
2. Check the channel probe to confirm the Telegram transport shows connected or works.
3. If the runtime is healthy but Telegram is dead, investigate the token and configuration. Remember, Telegram relies on a token from config or environment, not a login flow.
4. If you see 'telegram plugin not available', the issue is with plugin dependencies, not the bot token itself. This requires fixing the plugin load path.

What the Evidence Confirms

• An OpenClaw Telegram bot requires a running gateway plus a token in config/env. If either is missing, the bot won't work.
• The bot does not use openclaw channels login telegram like some other channels do.
• For rapid diagnosis, always examine runtime, probe, and channel status before asking for additional information from users or changing settings.

Confidence Level

• The diagnostic sequence for checking runtime, probes, and tokens is well-supported by documentation.
• The "bot stalls due to CPU spin" scenario is based on a bug report and should be treated as a strong possibility, not a guaranteed conclusion for every system.

Bottom line: When an OpenClaw Telegram bot fails, don't ask more questions or jump to config changes. Verify the gateway and runtime probes are healthy, then check the Telegram token in your config or environment. Telegram does not use a login flow—it pulls the token directly from configuration.

If the Bot Is Completely Silent

A completely unresponsive bot typically points to one of three failures:

• The gateway or runtime is not running, or its probe fails.
• The Telegram token is missing or incorrect in your config or environment.
• The Telegram plugin failed to load. A known issue reports the exact error telegram plugin not available, which means the plugin itself never initialized.

If the Bot Connects but Replies Stall

Evidence from bug reports suggests that gateway runtime problems—not token issues—are the likely culprit. One documented case shows Telegram replies stalling because the gateway enters a CPU spin state, essentially getting stuck in a processing loop.

The Correct Diagnostic Order

Follow this sequence to pinpoint the problem without chasing false leads:

1. Check gateway/runtime health first. Do not change configuration yet. Use the appropriate status commands to verify the baseline.
2. Check the channel probe to confirm the Telegram transport shows connected or works.
3. If the runtime is healthy but Telegram is dead, investigate the token and configuration. Remember, Telegram relies on a token from config or environment, not a login flow.
4. If you see 'telegram plugin not available', the issue is with plugin dependencies, not the bot token itself. This requires fixing the plugin load path.

What the Evidence Confirms

• An OpenClaw Telegram bot requires a running gateway plus a token in config/env. If either is missing, the bot won't work.
• The bot does not use openclaw channels login telegram like some other channels do.
• For rapid diagnosis, always examine runtime, probe, and channel status before asking for additional information from users or changing settings.

Confidence Level

• The diagnostic sequence for checking runtime, probes, and tokens is well-supported by documentation.
• The "bot stalls due to CPU spin" scenario is based on a bug report and should be treated as a strong possibility, not a guaranteed conclusion for every system.

Bottom line: When an OpenClaw Telegram bot fails, don't ask more questions or jump to config changes. Verify the gateway and runtime probes are healthy, then check the Telegram token in your config or environment. Telegram does not use a login flow—it pulls the token directly from configuration.