Plugins

Pyrogram embeds an **automatic** and lightweight plugin system that is meant to further simplify the organization of

large projects and to provide a way for creating pluggable components that can be **easily shared** across different

Prior to the plugin system, pluggable handlers were already possible. For instance, if you wanted to modularize your

applications, you had to do something like this...

Creating Plugins

Setting up your Pyrogram project to accommodate plugins is as easy as creating a folder and putting your files full of

handlers inside.

.. note:: This is the same example application `as shown above <#introduction>`_, written using the plugin system.

the ``plugins_dir`` parameter when creating a :obj:`Client <pyrogram.Client>`; you can put *any python file* in the

plugins folder and each file can contain *any decorated function (handlers)*. Your Pyrogram Client instance (in the

``main.py`` file) will **automatically** scan the folder upon creation to search for valid handlers and register them

for you.

Then you'll notice you can now use decorators, with only one limitation: within a single plugin file you must use

different names for each decorated function. That's right, you can apply the usual decorators to your callback functions

in a static way, i.e. **without having the Client instance around**: simply use ``@Client`` (Client class) instead of

the usual ``@app`` (Client instance) namespace and things will work just the same.