# How to Ask Questions Effectively

Cherry Studio is a free and open-source project. As the project grows, the workload of the project team is also increasing day by day. In order to reduce communication costs and be able to solve your problems quickly and efficiently, we hope everyone will try to handle the problems encountered according to the following steps and methods before asking questions, so that the project team can spend more time on maintenance and development. Thank you for your cooperation!

## 1. Documentation Review and Search

Most basic problems can basically be solved by carefully reading the documentation

* For software functions and usage issues, you can go to the [Feature Introduction](/docs/en-us/cherry-studio/preview.md) documentation;
* Frequently asked questions will be included in the [FAQ](/docs/en-us/question-contact/questions.md) page. You can first check the FAQ page to see whether there is a solution;
* More complex issues can be solved directly by searching or asking in the search box;
* Be sure to carefully read the tip boxes in each document, as they can help you avoid many problems;
* On GitHub's [Issue](https://github.com/CherryHQ/cherry-studio/issues) page to view or search for similar issues and solutions.

## 2. Search online and ask AI

For issues unrelated to client functions, such as model usage issues (e.g., model errors, answers not meeting expectations, parameter settings, etc.), it is recommended to first search online for relevant solutions, or describe the error content and problem to AI to find a solution.

## 3. Ask in the official community or open an issue on GitHub

If the above steps 1 and 2 do not find an answer or cannot solve your problem, you can go to the official [TG channel](https://t.me/CherryStudioAI),[Discord channel](https://discord.com/invite/wez8HtpxqQ),[QQ group ](#user-content-fn-1)[^1]\([one-click to join the group](https://qm.qq.com/cgi-bin/qm/qr?authKey=xe5nfGVZLMYnlJq%2F%2B4kN03YWcDBB2lnD7tc9rWus2mxS0JHUbOzk79cO7MYuqyGR\&k=UKVgl3YPHmwPaU8qeO1VG03NcUkACKsc\&noverify=0)) and describe the problem in detail to seek help.

1. If it is a model error, please provide a full screenshot of the interface and the console error information. Sensitive information can be obscured, but the model name, parameter settings, and error content must be retained in the screenshot. How to view console error information [click here](/docs/en-us/question-contact/questions.md#kong-zhi-tai-bao-cuo-cha-kan-fang-fa).
2. If it is a software bug, please provide<mark style="background-color:green;">a specific description of the error</mark>and<mark style="background-color:green;">detailed</mark>[<mark style="background-color:green;">reproduction</mark>](#user-content-fn-2)[^2]<mark style="background-color:green;">steps</mark>to make it easier for developers to debug and fix. If it is an occasional issue that cannot be reproduced, please describe in as much detail as possible the relevant scene, background, and configuration parameters when the problem occurs.\
   In addition, you also need to include<mark style="background-color:green;">platform information</mark>(Windows, Mac, or Linux),<mark style="background-color:green;">software version number</mark>and other information in the issue description.

{% hint style="success" %}
**Request documentation or provide documentation suggestions**

You can contact the TG channel `@Wangmouuu` or QQ (`1355873789`), or send an email to:`sunrise@cherry-ai.com`.
{% endhint %}

[^1]: Group number: 611659451

[^2]: that is, the (error) happens again


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cherry-ai.com/docs/en-us/question-contact/ask.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
