Discord & Telegram channels not connecting (Windows 11, AutoClaw v0.3.0)

[blazing wolf]

Configured both Discord and Telegram bots — gateway says "configured, enabled automatically" but never actually connects. Zero connection logs, no errors. Webchat works fine.

Verified:

Both bot tokens valid (tested via API)
Config correct (enabled, dmPolicy open, allowFrom )
Multiple full restarts — same result
skills.allowBundled set to [""] — no effect
Also: Config keeps resetting on app restart (saves to openclaw.runtime.json instead of openclaw.json, tool settings revert).

Any help appreciated!

[dire token]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[worn pumice]

This smells like the gateway is not loading/mounting the channel plugins or not reading the config file you’re editing, not a Discord/Telegram token problem.

A few quick checks:

openclaw --version
openclaw gateway status
openclaw status --all
openclaw status --deep
openclaw channels status --probe
openclaw doctor

Please paste those outputs with tokens redacted.

Key things I’d look for:

• If status --deep has an empty Channels table, that matches a prior “configured but never mounted at runtime” class of bug. (github.com)
• If logs show missing deps like Cannot find module 'grammy' or @buape/carbon, that’s a bundled plugin dependency/install problem. (github.com)
• skills.allowBundled won’t fix this — Discord/Telegram are channel plugins, not skills.
• OpenClaw’s persistent config is normally ~/.openclaw/openclaw.json; if AutoClaw is writing openclaw.runtime.json and changes revert on restart, the app/wrapper may be generating ephemeral runtime config instead of updating the canonical config. OpenClaw docs say config is read from ~/.openclaw/openclaw.json. (docs.openclaw.ai)

Also: AutoClaw version isn’t enough here — please include the actual openclaw --version. On Windows, WSL2 is still the recommended stable path for the full gateway experience. (docs.openclaw.ai)

[blazing wolf]

Update: Checked the extensions folder — AutoClaw only bundles these channel plugins:

openclaw-lark
openclaw-qqbot
openclaw-weixin
dingtalk-connector
wecom
Discord and Telegram channel plugins are NOT included. That's why the gateway shows "configured, enabled automatically" but never connects — the plugin code simply doesn't exist in this build.

Is there a way to install Discord/Telegram channel plugins separately, or are they only available in the standard OpenClaw (non-AutoClaw) build?

[worn pumice]

Yep — that diagnosis makes sense. I’d stop chasing token/config now.

Current standard OpenClaw does include Discord and Telegram as bundled channel extensions. If AutoClaw’s extensions folder only has Lark/QQ/Weixin/DingTalk/WeCom, then that AutoClaw build is missing the channel runtime code, so configured, enabled automatically can’t actually start anything.

Practical answer:

• Telegram: looks bundled-only in current OpenClaw, not a normal separately installable official plugin.
• Discord: there is/was an @openclaw/discord package path for custom/older installs, but compatibility depends on the host OpenClaw version. You can try:

openclaw plugins install npm:@openclaw/discord
openclaw doctor --fix
openclaw gateway restart

…but I would not expect this to solve Telegram, and it may not work with AutoClaw if their host/plugin API differs.