Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Telegram channel never initializes on Windows - no telegram logs on gateway start [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#57325•Fetched 2026-04-08 01:50:59
View on GitHub
Comments
2
Participants
2
Timeline
6
Reactions
0
Author
ahmetsemih14638-byteahmetsemih14638-byte
Participants
ahmetsemih14638-byteahmetsemih14638-bytevincentkocvincentkoc
Timeline (top)
commented ×2labeled ×2closed ×1locked ×1

Telegram channel is configured correctly (enabled: true, botToken set, accounts.default configured) but gateway never starts the Telegram provider on Windows. No telegram-related log lines appear on gateway startup. channels list shows empty, status shows Running: No.

Root Cause

Telegram channel is configured correctly (enabled: true, botToken set, accounts.default configured) but gateway never starts the Telegram provider on Windows. No telegram-related log lines appear on gateway startup. channels list shows empty, status shows Running: No.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Telegram channel is configured correctly (enabled: true, botToken set, accounts.default configured) but gateway never starts the Telegram provider on Windows. No telegram-related log lines appear on gateway startup. channels list shows empty, status shows Running: No.

Steps to reproduce

  1. Install OpenClaw 2026.3.28 on Windows 10
  2. Configure Telegram channel with botToken and accounts.default
  3. Start gateway
  4. Run: openclaw channels list
  5. Observe: Telegram channel never appears, no telegram logs on startup

Expected behavior

Telegram channel should start when gateway boots, appear in "openclaw channels list", and respond to incoming Telegram messages.

Actual behavior

Telegram channel never starts. "openclaw channels list" shows empty. No telegram-related log lines appear on gateway startup. Bot does not respond to any Telegram messages.

OpenClaw version

2026.3.28

Operating system

Windows 10 (10.0.19045 x64)

Install method

npm global

Model

deepseek/deepseek-chat,GLM 4.7

Provider / routing chain

OpenClaw -> DeepSeek API

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

Fix Plan

To resolve the issue of the Telegram channel not starting on Windows, we need to ensure that the Telegram provider is properly configured and initialized. Here are the steps to follow:

  • Check the config.json file for the correct Telegram configuration:
{
  "channels": {
    "telegram": {
      "enabled": true,
      "botToken": "YOUR_BOT_TOKEN",
      "accounts": {
        "default": {
          "username": "YOUR_TELEGRAM_USERNAME"
        }
      }
    }
  }
}
  • Verify that the botToken and username are correct and match the ones provided by Telegram.
  • Update the gateway.js file to include the Telegram provider:
const { TelegramProvider } = require('openclaw-providers');

// ...

const providers = [
  // ...
  new TelegramProvider({
    botToken: config.channels.telegram.botToken,
    accounts: config.channels.telegram.accounts,
  }),
];

// ...
  • Ensure that the openclaw-providers package is installed and up-to-date:
npm install openclaw-providers@latest
  • Restart the gateway and check the logs for any Telegram-related errors.

Verification

To verify that the fix worked, run the following command:

openclaw channels list

The Telegram channel should now appear in the list, and the gateway should respond to incoming Telegram messages.

Extra Tips

  • Make sure to keep the botToken and username confidential to avoid security issues.
  • If you're still experiencing issues, try checking the Telegram API documentation for any updates or changes to the bot token or authentication process.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Telegram channel should start when gateway boots, appear in "openclaw channels list", and respond to incoming Telegram messages.

#api#conversation history#tool integration#LLM response#prompt template

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING