mirror of
https://github.com/QwenLM/qwen-code.git
synced 2026-04-30 20:50:34 +00:00
90236465d3
- Add GroupGate class for group access control with three policies: disabled (default), allowlist, and open - Implement mention gating: bot only responds when @mentioned or replied to in groups (configurable per-group) - Extend Envelope type with isGroup, isMentioned, isReplyToBot fields - Update TelegramAdapter to detect group context and mentions - Add comprehensive documentation for group chat setup and troubleshooting This enables using Qwen Code bots in Telegram groups with fine-grained access control and mention-based activation to prevent noise. Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
108 lines
4.1 KiB
Markdown
108 lines
4.1 KiB
Markdown
# Telegram
|
|
|
|
This guide covers setting up a Qwen Code channel on Telegram.
|
|
|
|
## Prerequisites
|
|
|
|
- A Telegram account
|
|
- A Telegram bot token (see below)
|
|
|
|
## Creating a Bot
|
|
|
|
1. Open Telegram and search for [@BotFather](https://t.me/BotFather)
|
|
2. Send `/newbot` and follow the prompts to choose a name and username
|
|
3. BotFather will give you a bot token — save it securely
|
|
|
|
## Finding Your User ID
|
|
|
|
To use `senderPolicy: "allowlist"` or `"pairing"`, you need your Telegram user ID (a numeric ID, not your username).
|
|
|
|
The easiest way to find it:
|
|
|
|
1. Search for [@userinfobot](https://t.me/userinfobot) on Telegram
|
|
2. Send it any message — it will reply with your user ID
|
|
|
|
## Configuration
|
|
|
|
Add the channel to `~/.qwen/settings.json`:
|
|
|
|
```json
|
|
{
|
|
"channels": {
|
|
"my-telegram": {
|
|
"type": "telegram",
|
|
"token": "$TELEGRAM_BOT_TOKEN",
|
|
"senderPolicy": "allowlist",
|
|
"allowedUsers": ["YOUR_USER_ID"],
|
|
"sessionScope": "user",
|
|
"cwd": "/path/to/your/project",
|
|
"instructions": "You are a concise coding assistant responding via Telegram. Keep responses short.",
|
|
"groupPolicy": "disabled",
|
|
"groups": {
|
|
"*": { "requireMention": true }
|
|
}
|
|
}
|
|
}
|
|
}
|
|
```
|
|
|
|
Set the bot token as an environment variable:
|
|
|
|
```bash
|
|
export TELEGRAM_BOT_TOKEN=<your-token-from-botfather>
|
|
```
|
|
|
|
Or add it to a `.env` file that gets sourced before running.
|
|
|
|
## Running
|
|
|
|
```bash
|
|
qwen channel start my-telegram
|
|
```
|
|
|
|
Then open your bot in Telegram and send a message. You should see "Working..." appear immediately, followed by the agent's response.
|
|
|
|
## Group Chats
|
|
|
|
To use the bot in Telegram groups:
|
|
|
|
1. Set `groupPolicy` to `"allowlist"` or `"open"` in your channel config
|
|
2. **Disable privacy mode** in BotFather: `/mybots` → select your bot → Bot Settings → Group Privacy → Turn Off
|
|
3. Add the bot to a group. If it was already in the group, **remove and re-add it** (Telegram caches privacy settings from when the bot joined)
|
|
4. If using `groupPolicy: "allowlist"`, add the group's chat ID to `groups` in your config
|
|
|
|
By default, the bot requires an @mention or a reply to respond in groups. Set `"requireMention": false` for a specific group to make it respond to all messages (useful for dedicated task groups). See [Group Chats](./overview#group-chats) for full details.
|
|
|
|
## Tips
|
|
|
|
- **Keep instructions concise-focused** — Telegram has a 4096-character message limit. Adding instructions like "keep responses short" helps the agent stay within bounds.
|
|
- **Use `sessionScope: "user"`** — This gives each user their own conversation. Use `/reset` to start fresh.
|
|
- **Restrict access** — Use `senderPolicy: "allowlist"` for a fixed set of users, or `"pairing"` to let new users request access with a code you approve via CLI. See [DM Pairing](./overview#dm-pairing) for details.
|
|
|
|
## Message Formatting
|
|
|
|
The agent's markdown responses are automatically converted to Telegram-compatible HTML. Code blocks, bold, italic, links, and lists are all supported.
|
|
|
|
## Troubleshooting
|
|
|
|
### Bot doesn't respond
|
|
|
|
- Check that the bot token is correct and the environment variable is set
|
|
- Verify your user ID is in `allowedUsers` if using `senderPolicy: "allowlist"`, or that you've been approved if using `"pairing"`
|
|
- Check the terminal output for errors
|
|
|
|
### Bot doesn't respond in groups
|
|
|
|
- Check that `groupPolicy` is set to `"allowlist"` or `"open"` (default is `"disabled"`)
|
|
- If using `"allowlist"`, verify the group's chat ID is in the `groups` config
|
|
- Make sure **Group Privacy is turned off** in BotFather — without this, the bot can't see non-command messages in groups
|
|
- If you changed privacy mode after adding the bot to a group, **remove and re-add the bot** to the group
|
|
- By default, the bot requires an @mention or a reply. Send `@yourbotname hello` to test
|
|
|
|
### "Sorry, something went wrong processing your message"
|
|
|
|
This usually means the agent encountered an error. Check the terminal output for details.
|
|
|
|
### Bot takes a long time to respond
|
|
|
|
The agent may be running multiple tool calls (reading files, searching, etc.). The "Working..." indicator shows while the agent is processing. Complex tasks can take a minute or more.
|