Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Feature]: Feature Request: Support Multiple Telegram Bot Configurations [1 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#62946•Fetched 2026-04-09 08:00:20
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Author
noobsmokernoobsmoker
Participants
noobsmokernoobsmoker
Timeline (top)
labeled ×1

Allow configuring multiple Telegram bots in OpenClaw, each routing to different agent sessions.

Use Case

User wants to run multiple Telegram bots (e.g., @tele_bot, @tele2_bot), each connecting to a different OpenClaw agent session.

Current Limitation

OpenClaw only supports one telegram channel key in the config, preventing users from running multiple Telegram bots simultaneously.

Proposed Solution

  1. Support custom channel keys (e.g., telegram, telegram-2, or named like telegram-bot1)
  2. Each Telegram channel instance should support independent settings: • botToken (required per bot) • agentId (routes messages to specific agent session) • allowFrom (user allowlist) • dmPolicy, groupPolicy, etc.

Example Config

{ "channels": { "telegram": { "enabled": true, "botToken": "bot_token_1", "agentId": "agent-1" }, "telegram-2": { "enabled": true, "botToken": "bot_token_2", "agentId": "agent-2" } } }

Priority

High - Blocks multi-bot deployments.

Root Cause

Allow configuring multiple Telegram bots in OpenClaw, each routing to different agent sessions.

Use Case

User wants to run multiple Telegram bots (e.g., @tele_bot, @tele2_bot), each connecting to a different OpenClaw agent session.

Current Limitation

OpenClaw only supports one telegram channel key in the config, preventing users from running multiple Telegram bots simultaneously.

Proposed Solution

  1. Support custom channel keys (e.g., telegram, telegram-2, or named like telegram-bot1)
  2. Each Telegram channel instance should support independent settings: • botToken (required per bot) • agentId (routes messages to specific agent session) • allowFrom (user allowlist) • dmPolicy, groupPolicy, etc.

Example Config

{ "channels": { "telegram": { "enabled": true, "botToken": "bot_token_1", "agentId": "agent-1" }, "telegram-2": { "enabled": true, "botToken": "bot_token_2", "agentId": "agent-2" } } }

Priority

High - Blocks multi-bot deployments.

RAW_BUFFERClick to expand / collapse

Summary

Allow configuring multiple Telegram bots in OpenClaw, each routing to different agent sessions.

Use Case

User wants to run multiple Telegram bots (e.g., @tele_bot, @tele2_bot), each connecting to a different OpenClaw agent session.

Current Limitation

OpenClaw only supports one telegram channel key in the config, preventing users from running multiple Telegram bots simultaneously.

Proposed Solution

  1. Support custom channel keys (e.g., telegram, telegram-2, or named like telegram-bot1)
  2. Each Telegram channel instance should support independent settings: • botToken (required per bot) • agentId (routes messages to specific agent session) • allowFrom (user allowlist) • dmPolicy, groupPolicy, etc.

Example Config

{ "channels": { "telegram": { "enabled": true, "botToken": "bot_token_1", "agentId": "agent-1" }, "telegram-2": { "enabled": true, "botToken": "bot_token_2", "agentId": "agent-2" } } }

Priority

High - Blocks multi-bot deployments.

Problem to solve

This will break user gateway and openclaw if they ask agent to set this system. The doctor will be unable to restore the build and open gateway. This is a technical barrier.

Proposed solution

botToken (required per bot) agentId (routes messages to session) Custom channel names.

Alternatives considered

No response

Impact

Multi agent telegram users. Severe Always Breaks gateway, dash, prevents doctor fix

Evidence/examples

No response

Additional information

No response

extent analysis

TL;DR

To support multiple Telegram bots in OpenClaw, each routing to different agent sessions, modify the configuration to allow custom channel keys with independent settings.

Guidance

  • Modify the OpenClaw configuration to support multiple Telegram channels with unique names (e.g., "telegram", "telegram-2") and independent settings.
  • Ensure each Telegram channel instance has required settings such as botToken and agentId.
  • Update the configuration to include custom channel names and settings, as shown in the proposed example config.
  • Test the modified configuration to verify that multiple Telegram bots can run simultaneously and route messages to different agent sessions.

Example

{
  "channels": {
    "telegram": {
      "enabled": true,
      "botToken": "bot_token_1",
      "agentId": "agent-1"
    },
    "telegram-2": {
      "enabled": true,
      "botToken": "bot_token_2",
      "agentId": "agent-2"
    }
  }
}

Notes

The proposed solution requires modifying the OpenClaw configuration to support custom channel keys and independent settings for each Telegram channel instance.

Recommendation

Apply workaround by modifying the OpenClaw configuration to support multiple Telegram channels with unique names and independent settings, as this will allow users to run multiple Telegram bots simultaneously and route messages to different agent sessions.

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…
#logging issue#authentication issue#prompt issue#agent setup#task chaining

Still need to ship something?

×6

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

Back to top recommendations

TRENDING