How you reach us depends on what you need.
For "how do I…", architecture sanity-checks, capacity questions, sharing what you built, or open-ended brainstorming — use Discussions or chat with us on Discord. The issue tracker is reserved for actionable bug reports and concrete feature proposals.
Open a Bug report. The form requires the minimum fields we need to triage: version, deployment mode, OS, LLM provider, repro steps, and expected vs. actual behavior. Reports without those fields are slow to action.
Before filing:
- Search existing issues and Discussions for duplicates.
- Confirm the behavior contradicts the Public API & Stability section. Behavior of internal surfaces (e.g. database schema, gateway-injected headers,
/admin/*routes) can change without notice and isn't tracked as a bug.
Open a Feature request. The form asks you to declare which surface from the SemVer contract the feature touches — this scopes the conversation early.
Out-of-scope contributions get a polite decline with a pointer to the relevant section of CONTRIBUTING.md. We don't merge features out of guilt; the issue thread is where to make the case before writing code.
Do not open a public issue. Use GitHub Security Advisories — reports are private to maintainers until a coordinated disclosure. Full policy in SECURITY.md.
We aim to acknowledge every issue and PR within five business days — not necessarily with a fix or merge, but with a triage decision (accepted / needs-info / out-of-scope) so you know what's happening. If a week goes by without any response, ping the thread or open a Discussion — we'd rather be reminded than ghost you.
See MAINTAINERS.md for the current maintainer roster, areas of ownership, and how triage rotation works.