> For the complete documentation index, see [llms.txt](https://docs.fylr.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fylr.io/for-system-administrators/configuration/custom-plugin.md).

# Load Custom Plugins

Assuming you installed fylr via docker-compose.

1. Have a plugin folder with fylr's unix user id:

```bash
mkdir plugins
chown 1000 plugins
```

2. Connect the new folder via `docker-compose.yml`

```yaml
  fylr:
    ...
    volumes:
      - "./plugins:/fylr/files/plugins/custom"
```

3. Add the new plugin path to `fylr.yml`

```yaml
fylr:
[...]
  plugin:
    # load plugins at startup. the loader crawls the given directories
    # and loads given files for plugin config files, ending in ".yml".
    # "*" and "?" are allowed as placeholders, unmatched directories or
    # files are silently skipped.
    paths:
      - "/fylr/files/plugins/custom"
      - [...other directory...]
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.fylr.io/for-system-administrators/configuration/custom-plugin.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.