How VibeGuard commands work
VibeGuard commands run inside Telegram groups and private admin flows, depending on the feature and the group’s settings.
Each Telegram group has its own command behavior because VibeGuard is scoped by group. A public group can enable anti-spam, anti-raid, and purge commands. A creator group can focus on recaps and profiles. A marketplace group can keep posting and link controls stricter. A multi-group network can add grid commands only after admins explicitly configure a chat grid.
Commands may be unavailable for three normal reasons: the feature is disabled, the user does not have enough command access, or the bot does not have the Telegram permissions needed to perform the action.
Command access and permissions
Owners can control who can run sensitive commands. Command access can depend on VibeGuard rank, named users, Telegram admin rights, topic scope, and grid scope where relevant.
For example, a moderator may be allowed to warn and mute, while only owners can ban, purge, change filters, or edit command access. Security Center can show command access settings, audit access changes, and help admins understand why a command failed.
Telegram permissions still matter. Deleting messages requires delete rights. Muting, restricting, kicking, or banning members requires member restriction rights. Join request workflows require the relevant approval permissions. Invite-link and lockdown actions require the proper Telegram admin rights.
Telegram bot commands list for moderation and safety
Use these command families when the group needs fast admin action, spam cleanup, or incident response.
| Command area | Common commands | Use it for |
|---|---|---|
| Warnings | /warn, /warnings, /unwarn | Issue or remove warnings with optional reason and expiry. |
| Mutes | /mute, /unmute, /mutes | Restrict writing for a duration and review active mutes. |
| Bans | /ban, /unban, /banlist, /amnesty | Ban, unban, review bans, and handle controlled amnesty flows. |
| Kicks | /kick, /silentkick | Remove a user without creating a permanent ban. |
| Purges | /purge, /purge_silent, /del, /cleanup | Bulk delete recent messages while respecting Telegram limits. |
| Command access | /access, /myaccess, /accesslog | Configure or review command availability by role and policy. |
Serious moderation actions should include reasons where possible. Cases, appeals, and audit logs help admins review decisions later instead of relying on memory.
Safety, raid, filter, and threat commands
Safety commands help admins test, tune, and respond to risky behavior.
| Command area | Common commands | Use it for |
|---|---|---|
| Raid response | /raidmode, /lockdown, /unlockdown, /raidstatus | Check raid state, start stronger protection, and recover after incidents. |
| Filters | /filters, /filter_add, /filter_test | View, add, and test anti-spam or safety rules. |
| Link controls | /allowlink, /blocklink, /links | Manage link allowlists and blocklists. |
| Threat review | /threat, /scam, /spamdb, /threat_report | Check, report, review, or appeal threat entries. |
| Grid moderation | /grid, /gban, /gmute, /gkick | Run grid-scoped actions only when chat-grid security is explicitly enabled. |
| Status and diagnostics | Security Center commands or buttons | Review rules, incidents, missing permissions, and failed actions. |
Start safety rules in audit mode when possible. Audit mode lets admins see what VibeGuard would catch before deleting messages, muting members, banning users, or changing group permissions.
AI recap, profile, and group memory commands
VibeGuard’s recap commands help members and admins catch up on busy chats and tune group memory.
Representative recap commands include /overview, /describe, /overviewtime, /nickname, /description, /gender, /chatdescription, /prompt, /bestof, /random, /balance, /report, /style, /main, /toggle, and /wish.
Use /overview for group summaries, /describe as a reply-based media description flow, /bestof for highlights, and /balance or quota-related commands to understand usage where enabled.
Profile commands help members and admins recognize people across name changes. Common profile behavior includes profile, my profile, profile lookup by @username, and numeric ID lookup such as id123.
Group AI prompt usage is controlled by product settings and quotas. Each group member can use up to 10 AI help/prompts for free. AI responses should stay controlled through the VibeGuard experience and should not be treated as automatic public group replies unless admins explicitly configure that workflow.
Community commands: music, horoscope, and relationship tools
Community commands should come after the group is safe and should stay enabled only where they fit the group culture.
Music discovery supports commands such as /search, /post, /song, /settings, /allow, and /deny, with group-level permissions for who can search, who can post, and which providers are enabled.
Horoscope supports horoscope, direct zodiac sign names, English sign aliases, and zodiac symbol aliases. Daily output can be cached, and AI styling should degrade gracefully if AI styling is unavailable.
Relationship and pairing commands belong in the relationship modules guide. These features can support invites, marriages, pairings, valentines, opt-outs, and social mechanics, but they should remain feature-flagged and admin-controlled.
Advanced opt-in modules should not be surfaced in the main command reference. Keep them gated, clearly documented, and unavailable unless a group explicitly enables them.
Command troubleshooting
If a command does not work, check these first.
The feature may be disabled for this group. Ask an owner to check feature flags or Security Center.
The user may not have enough command access. Some commands require owner, admin, moderator, rank, topic, or grid-level access.
The bot may be missing Telegram permissions. Deletion, restriction, banning, join request, and invite-link actions require specific Telegram admin rights.
The command may need a reply, mention, username, ID, duration, or reason. Reply-based commands are especially common for moderation and media description flows.
The command may belong to another page. Setup commands, anti-spam rules, anti-raid configuration, AI quotas, and relationship modules have dedicated docs.
FAQ
What commands does VibeGuard support?
VibeGuard supports command families for moderation, safety, recaps, profiles, governance, AI prompts, music discovery, horoscope, relationships, and admin control. Availability depends on the group’s enabled features and command access settings.
Why does a command work in one group but not another?
VibeGuard is group-scoped. Each Telegram group has its own settings, feature flags, command access, moderation state, AI usage, and Mini App context.
Who can use moderation commands like warn, mute, ban, kick, and purge?
Owners decide command access. Sensitive commands can require VibeGuard rank, Telegram admin rights, named-user access, topic scope, or grid scope. Destructive commands also require the bot to have the right Telegram permissions.
Are Russian command aliases supported?
Yes. VibeGuard can support Russian admin aliases where configured. On the English docs page, keep English commands primary and place Russian aliases in a collapsed alias view or on the Russian docs page.
Are AI commands free?
VibeGuard has a free forever version for every group. Each group member can use up to 10 AI help/prompts for free, with paid expansion only when the group needs more AI attention, higher usage, advanced security, automation, or multi-group control.
Add VibeGuard, enable the command families your group needs, and keep sensitive actions under admin control.