# Extensions You might have [a custom tasks](tasks.md#creating-a-custom-task) or [event listeners](runner.md#events) that is not included in the default GrumPHP project. It is possible to group this additional GrumPHP configuration in an extension. This way you can centralize this custom logic in your own extension package and load it wherever you need it. The configuration looks like this: ```yaml # grumphp.yml grumphp: extensions: - My\Project\GrumPHPExtension ``` The configured extension class needs to implement `GrumPHP\Extension\ExtensionInterface`. Since GrumPHP is using the [symfony/dependency-injection](https://symfony.com/doc/current/service_container.html) internally to configure all resources, a GrumPHP extension can append multiple configuration files to the container configuration. We support following loaders: YAML, XML, INI, GLOB, DIR. *Note:* We don't support the PHP or CLOSURE loaders to make sure your extension is compatible with our grumphp-shim PHAR distribution. All dependencies get scoped with a random prefix in the PHAR, making these loaders not usable in there. Example extension: ```php