Skip to main content
Start with Troubleshooting. Most reports are answered by one of the fifteen symptoms listed there, and checking it first is the fastest route to an answer.

​
Where do you report what?

Bugs

Something behaves differently than this documentation says. Open a GitHub issue.

Questions and ideas

How do I, should I, would you consider. Open an issue and label it a question.

Security vulnerabilities

Follow the security policy. Never open a public issue for a vulnerability.

Feature requests

Feature work is frozen until 1.0.0, so open an issue to record it rather than a pull request.

​
Before you open an issue

Four details turn a report into something reproducible.
Never paste the output of docker compose config into an issue. It contains your resolved database password. Redact secrets from logs before posting them.

​
Reporting a documentation problem

A page that is wrong is a bug like any other. Open an issue naming the page and the incorrect statement, or open a pull request against /docs directly. Both are welcome. If an AI assistant answered a question about asobeast incorrectly, that usually means a page is ambiguous rather than that the assistant is broken. Say which question you asked, and it becomes a fixable documentation issue.
Last modified on July 31, 2026