11 replies

Second agent with Telegram Channel

✅Solved

I created a second agent named "kitchenmaid" and a Telegram Bot for it.

I have the following configuration:

"channels": {
    "telegram": {
      "enabled": true,
      "commands": {
        "nativeSkills": true
      },
      "dmPolicy": "pairing",
      "accounts": {
         "default": {
           "botToken": "TOKEN1" 
           
         },
          "kitchenaid": {
            "botToken": "TOKEN2
            
          }
      },
      "streaming": "partial"
    },
...
 
"bindings": [
    {
      "agentId": "main",
      "match": { "channel": "telegram", "accountId": "default" }
    },
    {
      "agentId": "kitchenaid",
      "match": { "channel": "telegram", "accountId": "kitchenaid" }
    }
  ]
...

"channels": {
    "telegram": {
      "enabled": true,
      "commands": {
        "nativeSkills": true
      },
      "dmPolicy": "pairing",
      "accounts": {
         "default": {
           "botToken": "TOKEN1" 
           
         },
          "kitchenaid": {
            "botToken": "TOKEN2
            
          }
      },
      "streaming": "partial"
    },
...
 
"bindings": [
    {
      "agentId": "main",
      "match": { "channel": "telegram", "accountId": "default" }
    },
    {
      "agentId": "kitchenaid",
      "match": { "channel": "telegram", "accountId": "kitchenaid" }
    }
  ]
...

I can talk to the seconds agent, but

1.) There was no paring request/code
2.) I cannot use slash commands in the Telegram channel of the second agent

What is wrong?

Solution

That behavior is expected.

- With multi-account Telegram, a bunch of access-control knobs (including

dmPolicy

dmPolicy

) are effectively account-scoped. Putting

dmPolicy: "pairing"

dmPolicy: "pairing"

only at

channels.telegram.dmPolicy

channels.telegram.dmPolicy

can lead to “it works but no pairing gate” depending on how the account inherits/overrides.
- Slash commands/directives are authorization-gated. Until your Telegram sender is authorized (via pairing/allowlist),

/...

/...

often gets treated as plain text. Once you approved the pairing request, commands started working — exactly as designed.

Docs for reference:
- Telegram channel: https://docs.openclaw.ai/channels/telegram
- Pairing: https://docs.openclaw.ai/channels/pairing
- Slash commands: https://docs.openclaw.ai/tools/slash-commands
- Multi-agent routing: https://docs.openclaw.ai/concepts/multi-agent

If this fixed it, please right-click the solution message → Apps → Mark Solution so Answer Overflow can index it for the next person.

Jump to solution

FotC�

Friends of the Crustacean 🦞🤝•2w ago•

11 replies

Norbert

Second agent with Telegram Channel

✅Solved

I created a second agent named "kitchenmaid" and a Telegram Bot for it.

I have the following configuration:

"channels": {
    "telegram": {
      "enabled": true,
      "commands": {
        "nativeSkills": true
      },
      "dmPolicy": "pairing",
      "accounts": {
         "default": {
           "botToken": "TOKEN1" 
           
         },
          "kitchenaid": {
            "botToken": "TOKEN2
            
          }
      },
      "streaming": "partial"
    },
...
 
"bindings": [
    {
      "agentId": "main",
      "match": { "channel": "telegram", "accountId": "default" }
    },
    {
      "agentId": "kitchenaid",
      "match": { "channel": "telegram", "accountId": "kitchenaid" }
    }
  ]
...

"channels": {
    "telegram": {
      "enabled": true,
      "commands": {
        "nativeSkills": true
      },
      "dmPolicy": "pairing",
      "accounts": {
         "default": {
           "botToken": "TOKEN1" 
           
         },
          "kitchenaid": {
            "botToken": "TOKEN2
            
          }
      },
      "streaming": "partial"
    },
...
 
"bindings": [
    {
      "agentId": "main",
      "match": { "channel": "telegram", "accountId": "default" }
    },
    {
      "agentId": "kitchenaid",
      "match": { "channel": "telegram", "accountId": "kitchenaid" }
    }
  ]
...

I can talk to the seconds agent, but

1.) There was no paring request/code
2.) I cannot use slash commands in the Telegram channel of the second agent

What is wrong?

Solution

That behavior is expected.

- With multi-account Telegram, a bunch of access-control knobs (including

dmPolicy

dmPolicy

) are effectively account-scoped. Putting

dmPolicy: "pairing"

dmPolicy: "pairing"

only at

channels.telegram.dmPolicy

channels.telegram.dmPolicy

/...

/...

Jump to solution

Second agent with Telegram Channel

Second agent with Telegram Channel

Similar Threads

Similar Threads

Similar Threads