> 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/notation/brackets.md).
# Brackets
MuseScore provides **brackets** and a curly **brace** in the **Brackets** [palette](/3/basics/palettes.md) (Advanced [workspace](/3/basics/workspaces.md)).
When a new score is created using a template, MuseScore automatically sets the correct brackets.
## Add
To add a bracket or brace to systems, use one of two methods:
* Select a measure on the staff where you want the bracket/brace to start, and click the desired icon in a palette (double-click in versions prior to 3.4).
* Drag a bracket/brace icon from a palette on to the staff where you want the bracket/brace to start.
## Delete
* Select the bracket and press Del.
## Change
* Drag the desired icon from a palette onto an existing bracket/brace in the score.
## Edit
When you first apply a bracket it only spans one staff. To extend to other staves:
1. Enter [Edit mode](/3/basics/edit-mode.md#enter-exit).
2. Drag the handle downwards to span the required staves. The handle snaps into position, so exact placement is not required.
## Style
The default thickness and distance from the system of brackets and braces can be adjusted in [Format→ Style... → System](/3/formatting/layout-and-formatting.md#system).
In the **System Brackets** section, you can set the properties for the brackets in the two boxes on the left, and the properties for the braces in the two boxes on the right.
---
# 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/notation/brackets.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.