fix(telegram): include AccountId in native command context for multi-agent routing #2942
+2
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Great change! +1 for merging this. Would help out lots. |
…agent routing When running multiple Telegram bot accounts bound to different agents, the /new command (and other slash commands) would send confirmation messages via the wrong bot because the context was missing AccountId. The fix adds AccountId: route.accountId to the context payload in registerTelegramNativeCommands, matching how bot-message-context.ts handles regular messages. Fixes openclaw#2537
51d83bd to
0319bef
Compare
Contributor
lawrence565
pushed a commit
to lawrence565/moltbot
that referenced
this pull request
Jan 29, 2026
HirokiKobayashi-R
pushed a commit
to HirokiKobayashi-R/moltbot
that referenced
this pull request
Jan 29, 2026
mfgering
pushed a commit
to mfgering/mfg_moltbot
that referenced
this pull request
Jan 29, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
When running multiple Clawdbot agents with the same Telegram bot token (multi-agent setup), native commands like
/startwere not being routed to the correct agent. TheAccountIdwas not being passed through the command context, causing the routing logic to fail.Solution
Added
AccountIdto the context object passed to native command handlers in the Telegram channel plugin. This ensures multi-agent routing works correctly for native commands, consistent with how regular messages are handled.Changes
src/channels/telegram/telegram-plugin.ts: IncludeAccountIdin the context object passed tohandleNativeCommand()Testing
Tested in a multi-agent environment where two agents share the same Telegram bot token. Native commands now route correctly to the appropriate agent based on AccountId.