Bot To Bot
Telegram allows for bots to interact with other bots - this is known as bot-to-bot communcation.
By default, bots cannot interact with Rose's commands; she simply ignores them. But some use cases (eg, automation, AI bots, etc) might require this access - so it can be enabled separately.
Note
If you are using a custom clone Custom Clones, make sure to enable "bot to bot communication" in @botfather.
Different Bot to Bot modes
We support the following modes:
off: The default option; bots cannot use any Rose commands.admin: Admin bots are able to trigger Rose commands.all: All bots are able to trigger Rose commands.
You can change mode like this:
/bot2bot admin
Note
Being able to trigger a command does not necessarily mean the bot can change your settings; command reviews are enforced by default. More on this in the next section.
Command reviews
Once you've set the bot2bot setting to "admin" or "all", any admin bot is going to be able to start running commands
to
configure Rose. This could be risky; a malicious user could try to take advantage of an LLM bot in your group to get
them to change Rose's settings, or to promote themselves.
To protect against this, Rose expects all admin commands run by bots (eg, anything to change a setting) to go through an admin review first. This allows admins to double-check the command being run by the bot before it gets applied.
If you trust your bot enough and want to give them direct access to Rose's settings, you can choose to skip reviews entirely:
/bot2botskipreview on
To disable it, use the reverse:
/bot2botskipreview off
Note
Rose still respects admin permissions here; non-admin bots can't call admin commands. When skipreview is enabled, Rose will follow the bot's admin permissions; so removing the bot's ban permission will also stop them from using Rose to ban.
Triggering filters with bots
As mention in the help for filters, the {allow_bot} filling can be
used on a per-filter basis to allow bots to trigger that filter.