Skip to main content

Documentation Index

Fetch the complete documentation index at: https://chibi.bot/llms.txt

Use this file to discover all available pages before exploring further.

By default, Chibi is a private bot. However, misconfiguration can expose it to unauthorized users. This guide covers the essential settings to keep your bot secure.

​
Access Control (Whitelists)

The most effective way to secure your bot is to strictly limit who can use it.

​
User Whitelist

Use USERS_WHITELIST to specify exactly which Telegram users are allowed to interact with the bot.
  • By ID (Recommended): 123456789,987654321
  • By Username: @myusername,@friend
# .env
USERS_WHITELIST=123456789,@myusername

​
Group Whitelist

If you add the bot to a group, use GROUPS_WHITELIST to ensure it only responds in authorized groups. 
# .env
GROUPS_WHITELIST=-1001234567890

​
Privacy & Behavior Flags

Fine-tune how the bot behaves in public or shared spaces.

​
ANSWER_DIRECT_MESSAGES_ONLY

  • Default: True
  • Effect: If set to True, the bot will ignore messages in groups unless that specific group is in the GROUPS_WHITELIST. It will still respond to direct messages (DMs) from whitelisted users.
  • Use Case: Prevents the bot from being spammy or used by others if you accidentally add it to a public group.

​
ALLOW_BOTS

  • Default: False
  • Effect: If set to False, Chibi will ignore all messages sent by other bots.
  • Use Case: Prevents infinite loops where two bots keep replying to each other. Keep this disabled unless you have a specific reason.

​
Pre-start Security Checks

Chibi 1.6.1+ includes automatic security validations that run before the bot starts. These checks prevent dangerous configurations that could lead to security vulnerabilities.

​
What Gets Checked

CheckConditionAction
Private Mode WhitelistPUBLIC_MODE=False without USERS_WHITELISTBlocks startup - You must specify authorized users
Public + FilesystemPUBLIC_MODE=True with FILESYSTEM_ACCESS=TrueBlocks startup - Too risky for public access
Filesystem in GroupsFILESYSTEM_ACCESS=True with group usageShows warning - Consider if needed

​
Why These Checks Matter

  1. Prevent Unauthorized Access: Without a user whitelist in private mode, anyone who knows your bot’s username could interact with it and use your API credits.
  2. Protect Sensitive Data: Public bots with filesystem access could allow malicious users to read sensitive files from your server.
  3. Reduce Accidental Exposure: The warning for filesystem access in groups helps you reconsider before enabling potentially risky configurations.

​
Best Practices

  1. Never share your .env file. It contains your API keys and bot token.
  2. Use IDs over Usernames. Usernames can be changed; IDs are permanent. You can find your ID using bots like @userinfobot.
  3. Review Logs. Periodically check your logs for “Unauthorized access attempt” messages to see if strangers are trying to use your bot.
  4. Always configure USERS_WHITELIST in private mode - Chibi will prevent starting without it.
  5. Never enable FILESYSTEM_ACCESS in public mode - this is blocked by security checks.
  6. Keep ALLOW_BOTS=False unless specifically needed to prevent bot-to-bot loops.