> For the complete documentation index, see [llms.txt](https://rc.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rc.sunbird.org/engage/discussions.md).
# Discussion Forum
We have multiple channels available for the community to discuss use cases, ask for support from fellow community members, discuss existing features and brainstorm new ones.
{% hint style="info" %}
Reporting a bug or requesting a feature rather than starting a discussion? Go straight to the [Issue Tracker](https://github.com/Sunbird-RC/sunbird-rc-core/issues).
{% endhint %}
We encourage you to participate in the discussion forum, ask questions, and share your knowledge and experience with others. By working together, we can build a stronger and more engaged community.
General questions, ideas and enhancement suggestions, show-and-tell — anything worth keeping searchable. Discussions here often become issues, so it's the right place to float something before it's a formal request.
Join GitHub Discussions
Real-time chat — quick questions, debugging help, and informal conversation. Discord Invite
---
# 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://rc.sunbird.org/engage/discussions.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.