Getting Help
Version: 1.3 | Last updated: 2026-08-28
Whether you've hit a bug, have a question, or want to share an idea — here's where to go and what to expect.
For technical questions or bug reports
Where to get help?
You can raise technical questions or bug reports in the #support channel in our Discord or via email.
Before your post
- Read: Verify the behavior against documentation.
- Search: Check if a similar issue has been reported.
- Reproduce: Track the exact steps that trigger the problem.
- Isolate: Test if a specific config or environment causes the issue.
When you post
- Specify: Describe exactly what to fix and how to replicate it.
- Record: Provide screenshots, screen recordings, links, logs.
Never share your tokens, credentials, or private data! If your issue is security-related, email us directly.
After your post
We aim to acknowledge new messages within one business day.
We will investigate the issues with you via emails / conference calls.
For feature requests or product feedback
Where to get help?
You can send feature requests or product feedback in the #feedback channel in our Discord or via email.
Before your post
Please search existing ideas in Discord community first — upvoting or replying to an existing thread carries more signal than a duplicate post.
When you post
Please follow the template below to share your ideas:
- Subject — name the pain point, not the solution
- The pain — who experiences it, in what situation, and any current workaround
- The benefit — what would improve (time saved, better adoption, etc.)
- A possible solution — what capability would address it
Never share your tokens, credentials, or private data! If your issue is security-related, email us directly.
After your post
We will first discuss your posts within our product teams, then reply to your emails or label your Discord posts as below to reflect the status of the request:
| Label | Meaning |
|---|---|
new | Awaiting its first formal review. |
reviewing | Checking if the idea is feasible. |
candidate | Added to our upcoming project backlog. |
planned | Officially scheduled for an upcoming release. |
completed | Shipped! The idea is now live. |
duplicated | Someone else already suggested this. |
impracticable | Not possible or realistic at this stage. |
addressed | Solved indirectly through another feature. |