LevelChatLevelChatDocs
Community

Reference

Community

Where to ask questions and file issues.

Chat

  • Discord — fastest path to a human answer. Link in the footer of every page.
  • Design proposals + RFCs — email [email protected] with the proposal in the body or a PDF attachment. We reply within one business day and post pinned discussion threads on Discord for the proposals we accept.

Issues

  • Bugs + feature requests — email [email protected] with a short repro, expected vs actual behavior, and the request_id from any failing response. We file tracked tickets on receipt and reply with a ticket number you can quote in follow-ups.

Security

  • Security disclosures — email the address printed in the footer of every page (configurable via NEXT_PUBLIC_CONTACT_EMAIL, defaults to [email protected]). Please don't post security bugs in Discord. We respond within 24 h on weekdays.

Code of conduct

  • Be excellent to each other. Full text available on request — email [email protected].

Contributing

  • During the v0.3 preview window the source is distributed under NDA. Email [email protected] with your use case and we'll send back the mirror credentials plus the contribution guide. The TL;DR: branch off main, conventional commits, tests required, one-PR-per-area, signed-off-by trailer for non-trivial changes.
Community — LevelChat Docs