Commands Index
The commands below are grouped exactly by the active handler modules in backend/tg_client/dialogs/commands/handlers/. The current code exposes 10 handler groups and 104 registered commands.
Handler groups
| Handler group | Commands | Primary services | Page |
|---|---|---|---|
| Profile & Bootstrap Commands | 11 |
profile_service, bootstrap_service |
Profile & Bootstrap Commands |
| Chat Lists & Folder Commands | 11 |
chat_service, chat_list_service |
Chat Lists & Folder Commands |
| Chat Settings Commands | 20 |
chat_settings_command_service |
Chat Settings Commands |
| Dialog & Search Commands | 3 |
query_service, dialog_service |
Dialog & Search Commands |
| Media & Sticker Commands | 5 |
media_command_service, sticker_service, bootstrap_service |
Media & Sticker Commands |
| Members & Moderation Commands | 6 |
membership_service |
Members & Moderation Commands |
| Message Commands | 11 |
message_command_service |
Message Commands |
| Chat Admin & Invite Commands | 16 |
admin_service, invite_service |
Chat Admin & Invite Commands |
| Security & 2FA Commands | 11 |
security_command_service |
Security & 2FA Commands |
| Sessions & Privacy Commands | 10 |
settings_service |
Sessions & Privacy Commands |
Response model conventions
- Requests arrive over WebSocket as
{ "action": "<command>", ... }. - Most success responses are emitted as one
chat_updatepayload whosepayload.typeequals the command name. - Streaming commands are documented explicitly:
get_chats,get_recently_opened_chats,open_dialog. - Two-step async media commands are documented explicitly:
download_file,get_custom_emoji_media. - Error payloads are string-based and typically use
<command>_erroras the event type.