> For the complete documentation index, see [llms.txt](https://handbook.musescore.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.musescore.org/3/getting-started/get-support.md).
# Get Support
If you experience a problem while working with MuseScore, there are several ways to get help and support.
## Handbook
To access the Handbook:
* From the [MuseScore](https://musescore.org/en) website: select **Support ->** [**Handbook**](/3/readme.md) from the menu.
* From the MuseScore program: select **Help ->** [**Online Handbook**](/3/readme.md) from the menu.
You can browse through the Handbook using the menus, or do a [search](https://musescore.org/search/handbook).
## Context help
If you select an element in your score and press F1, a webpage opens displaying a list of links associated with that element in the [Handbook](/3/readme.md).
## Forums
MuseScore offers a number of on-line [Forums](https://musescore.org/forum) for user collaboration. You may be able to find an answer here to your problem among the existing posts. A [general search](https://musescore.org/search/site) of the website will return a list of relevant hits to all forums and the Handbook.
## How To's
Some tasks require the use of several different techniques. These can be difficult to find an answer for in the Handbook. Solutions for these *may* be found in the [How To's](https://musescore.org/en/howto)
## Post a question
If you cannot find the answer to your problem, you can ask a question in the [Support and bug reports](https://musescore.org/en/forum/6) forum.
When you post your question:
* Try to be as precise as you can, when you describe what you want to do, and which steps you have already tried.
* Attach the score that shows the problem. This will make it much easier for others to understand the problem — use the "File attachments" option at the bottom of the page, just above the **Save** and **Preview** buttons.
* You may format the text using [these tips](https://musescore.org/en/filter/tips).
## Report a bug
If you encounter something you think is a bug, the first step is to post it in the [Support and bug reports](https://musescore.org/en/forum/6) forum. This will allow others to help check if it is a genuine bug, and to advise workarounds, so you can continue your scorewriting. You will find more details on this in [Bug reports and Feature requests](/3/support/bug-reports-and-feature-requests.md).
## External links
* [How to write a good bug report: step-by-step instructions Isolate bug](https://musescore.org/en/node/309537) (MuseScore HowTo)
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://handbook.musescore.org/3/getting-started/get-support.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.