多 Bot Telegram 入站不触发非默认 Agent：核查 accountId 绑定与路由链路
问题/场景：多 Bot 配置下，非 default 账号消息被轮询消费但不触发 agent turn。前置条件：bindings 按 accountId 绑定多个 agent，Telegram accounts 已配置。实施步骤：用 channels status 观察 in:recent + audit failed → 校验 bindings/accountId 与 session lastAccountId 一致 → 对比 default 与非默认入站路径 → 先用 CLI/relay 兜底并记录日志定位。关键配置：bindings.match.accountId。验证：非默认 bot 收到消息后能触发目标 agent 回复。风险：目前 issue 已关闭需二次复现验证。来源：Issue #21189。
GITHUBDiscovered 2026-02-20Author jarviskulkarn-source
Prerequisites
- Multi-agent bindings are configured with distinct Telegram accountId values.
- You can run channel/session diagnostics (`openclaw channels status --probe`, session inspection).
Steps
- Send test messages to both default and non-default bots and compare whether agent turns are triggered.
- Inspect `openclaw channels status --probe` for `audit failed` on non-default account.
- Validate `bindings.match.accountId` against session metadata (`lastAccountId`) and inbound update account tag.
- Use temporary workaround (`openclaw agent --agent <id> --channel telegram --deliver`) while collecting logs for routing fix.
Commands
openclaw channels status --probeopenclaw gateway restartopenclaw agent --agent neo --channel telegram --deliver --message "test"Verify
Messages sent to non-default bot create/append target-agent session and produce outbound Telegram reply automatically.
Caveats
- Issue was closed by reporter; treat this as a diagnostic playbook until re-confirmed on latest version（需验证）.
- Do not leave CLI relay workaround as permanent architecture in production multi-tenant setups.
Source attribution
This tip is aggregated from community/public sources and preserved with attribution.
Open original source ↗