mirror of https://github.com/openclaw/openclaw.git
Merge c69b8e314f into 392ddb56e2
This commit is contained in:
commit
ed6cb5d59b
|
|
@ -499,6 +499,71 @@ Notes:
|
|||
- For stricter gating, set `agents.list[].groupChat.mentionPatterns` and keep
|
||||
group allowlists enabled for the channel.
|
||||
|
||||
## Multiple Telegram agents in one group
|
||||
|
||||
Put two or more Telegram bot accounts into a single group so users can
|
||||
@-mention the right agent for the job. Each bot needs its own BotFather token
|
||||
and a separate channel account.
|
||||
|
||||
```json5
|
||||
{
|
||||
agents: {
|
||||
list: [
|
||||
{
|
||||
id: "main",
|
||||
name: "Assistant",
|
||||
workspace: "~/.openclaw/workspace",
|
||||
identity: { name: "Assistant", emoji: "🤖" },
|
||||
},
|
||||
{
|
||||
id: "marketing",
|
||||
name: "MarketingBot",
|
||||
workspace: "~/.openclaw/workspace-marketing",
|
||||
identity: { name: "MarketingBot", emoji: "📢" },
|
||||
},
|
||||
],
|
||||
},
|
||||
channels: {
|
||||
telegram: {
|
||||
enabled: true,
|
||||
groupPolicy: "open",
|
||||
accounts: {
|
||||
default: {
|
||||
botToken: "TOKEN_FOR_ASSISTANT",
|
||||
groupPolicy: "open",
|
||||
allowFrom: [123456789],
|
||||
groupAllowFrom: [123456789],
|
||||
},
|
||||
marketing: {
|
||||
botToken: "TOKEN_FOR_MARKETING_BOT",
|
||||
groupPolicy: "open",
|
||||
allowFrom: [123456789],
|
||||
groupAllowFrom: [123456789],
|
||||
},
|
||||
},
|
||||
},
|
||||
},
|
||||
bindings: [
|
||||
{ agentId: "main", match: { channel: "telegram", accountId: "default" } },
|
||||
{ agentId: "marketing", match: { channel: "telegram", accountId: "marketing" } },
|
||||
],
|
||||
}
|
||||
```
|
||||
|
||||
Important setup steps:
|
||||
|
||||
1. **Disable Privacy Mode** for each bot in @BotFather (`/setprivacy` → Disable),
|
||||
otherwise bots only see `/commands` and direct replies in groups.
|
||||
2. **Re-add bots** to the group after changing privacy mode — Telegram caches
|
||||
the setting per-group and only applies changes on re-join.
|
||||
3. `groupPolicy` must be `"open"` (or `"allowlist"` with your user ID in
|
||||
`groupAllowFrom`). Note that `groupAllowFrom` filters by **sender user ID**,
|
||||
not by group chat ID. `allowFrom` is for DM access; `groupAllowFrom` is for
|
||||
group sender filtering (falls back to `allowFrom` when unset).
|
||||
4. Per-account `groupPolicy` overrides the top-level `channels.telegram.groupPolicy`.
|
||||
If you only want one account open for groups, set `groupPolicy` on that
|
||||
account and leave the top-level restrictive.
|
||||
|
||||
## Per-Agent Sandbox and Tool Configuration
|
||||
|
||||
Starting with v2026.1.6, each agent can have its own sandbox and tool restrictions:
|
||||
|
|
|
|||
Loading…
Reference in New Issue