因为我是配置子agent的时候才配置tg的导致出现问题，经过反复摸索知道了规律。
此时，主agent的robot是 botToken这个，而非默认agent 他的配置能根据数字编号识别。
"bindings": [
{
"agentId": "articlepublish",
"match": {
"channel": "telegram",
"accountId": "8732***"
}
}
],
"channels": {
"telegram": {
"enabled": true,
"dmPolicy": "allowlist",
"botToken": "86xxxxx:xxxxxx",
"allowFrom": [
"*"
],
"groupPolicy": "allowlist",
"streaming": "partial",
"accounts": {
"default": {
"dmPolicy": "pairing",
"groupPolicy": "allowlist",
"streaming": "partial"
},
"873xxx": {
"enabled": true,
"dmPolicy": "pairing",
"botToken": "873xxx:xxx",
"groupPolicy": "allowlist",
"streaming": "partial"
}
}
},
image.png
image.png
Workspace: C:\Windows\System32\UsersAdministrator.openclawworkspace\UsersAdministrator.openclawworkspace
Agent dir: ~\.openclaw\agents\main\agent
Model: ollamaqwen35lastest/qwen3.5:latest
Routing rules: 0
Routing: default (no explicit rules)
Providers:
- Telegram 873262****: configured
- Telegram default: configured
- QQ Bot default: configured
- articlepublish (articlePublish)
Workspace: ~\.openclaw\workspace-articlepublish
Agent dir: ~\.openclaw\agents\articlepublish\agent
Model: ollamaqwen35lastest/qwen3.5:latest
Routing rules: 1
Routing: Telegram 873262****
Providers:
- Telegram 873262****: configured
Routing rules map channel/account/peer to an agent. Use --bindings for full rules.
Channel status reflects local config/creds. For live health: openclaw channels status --probe.
C:\Users\Administrator>
