> For the complete documentation index, see [llms.txt](https://docs.mojo.trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mojo.trade/user-guide/feedback-and-support.md). # Feedback and Support Mojo gets better by hearing from the people using it. Tell us everything — what works, what's confusing, what's broken, what's missing. *** ### Where to reach us **Telegram group** — This is the primary support channel. The whole team is in there and reads every message. Bug reports, questions, feature requests, "wait, can Mojo also do this?" — all of it goes here. *** ### What makes a great bug report If you can include any of these, we'll fix things faster: 1. **What you were trying to do** — your intent, in your own words 2. **What you expected to happen** 3. **What actually happened** 4. **When it happened** — approximate time + which platform (Hyperliquid / on-chain spot / Polymarket) 5. **Screenshots or screen recording** — even a quick photo of your phone screen helps Don't let "perfect" be the enemy of "sent." A two-line message saying *"my multi-step ETH strategy stopped responding around 14:30 UTC, here's a screenshot"* is far more useful than a polished report we never receive. *** ### What we want most Bug reports matter. But the most valuable feedback is the stuff you'd never bother to write down: * **The strategy you wanted to build but couldn't figure out how to phrase** * **The moment you tried something and went *****"wait, it actually did that?"*** * **The thing you expected Mojo to do that it didn't** * **The friction in your workflow that Mojo could solve but doesn't yet** Send all of it. Half-formed thoughts are fine. The wilder your "what if Mojo could…" ideas, the better. *** ### What we'll do with your feedback * **Bugs** are triaged daily. Critical issues get addressed immediately. * **Product feedback** is reviewed by the team weekly. The highest-signal items influence the roadmap directly. * **Feature requests** are tracked and grouped. We won't build everything, but we'll always tell you what we're doing and why. The people who use Mojo day to day have an outsized influence on where it goes next. We read everything. If you tell us something matters, it gets discussed. If you find something broken, it gets fixed. **Thank you for building this with us.** --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.mojo.trade/user-guide/feedback-and-support.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.