agentscope-ai / agentscope-ai/QwenPaw
Feature: Add Telegram allowlist access control fields to Desktop GUI
- Vorherrschende Sprache
- TypeScript
- Sterne
- 35k
- Forks
- 3.1k
- Ø Merge
- 1 T. 13 Std.
- Gemergte PRs (30 T.)
- 228
Beschreibung
## Problem
The Telegram tab in the Desktop GUI only shows 5 fields: bot_token, base_url, http_proxy, http_proxy_auth, show_typing.
Users cannot set: allow_from, dm_policy, group_policy, access_control_dm, access_control_group, dm_disabled, group_disabled — all required for restrict-who-can-access-the-bot (allowlist/denylist).
These fields work in the backend and are shown for Matrix/imessage, but NOT for Telegram.
## Current Pain
To restrict access, users must manually edit config.json and add ALL of these:
```json
"telegram": {
"dm_policy": "allowlist",
"group_policy": "allowlist",
"access_control_dm": true,
"access_control_group": true,
"allow_from": [YOUR_TELEGRAM_ID]
}
Beitragsleitfaden
Rechercherichtung
Start by finding the Desktop GUI code that builds the Telegram tab and compare it with the Matrix/imessage tabs that already show access-control fields. Use the listed config.json keys as the required fields. Done means users can set the Telegram allowlist/denylist options in the GUI instead of manually editing config.json.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- python
- Bereich
- desktop
- Issue-Typ
- Feature
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Aktivitätsstatus
- Aktiv
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 66/100