> For the complete documentation index, see [llms.txt](https://chaoses-ib.gitbook.io/directory-opus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://chaoses-ib.gitbook.io/directory-opus/manual/customize/creating_your_own_buttons/editing_the_toolbar/dynamic_buttons.md).

# Dynamic Buttons

Dynamic buttons are a special type of button in Opus toolbars that behave differently in and out of Customize mode. In Customize mode they appear like any other button, and can be edited as normal - but in normal operation, the button itself disappears and is replaced by a dynamic list of items. For example, the Drive Buttons command on the supplied Drives toolbar is a normal button in Customize mode:

![](https://3597805814-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3XSZSwWow0fDf6fQJobd%2Fuploads%2Fgit-blob-bb67eac8eaca8fd1776b876037f91736e1c5dcf2%2Fdynamic_buttons_-_customize.png?alt=media)

But once the Customize dialog has been closed, we can see that the two buttons have disappeared, to be replaced with one button for each of the drives in the system:

![](https://3597805814-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3XSZSwWow0fDf6fQJobd%2Fuploads%2Fgit-blob-adcea61a9b66daa9fea5f8ab187976dd9ee1661a%2Fdynamic_buttons_-_no_customize.png?alt=media)

When out of Customize mode the generated buttons behave like normal ones, but the advantage is that you only need a single button to generate them - instead of having to define a button for each drive.

Dynamic buttons are also used for things like displaying your Favorite folders, your FTP sites, and Lister [layouts](/directory-opus/manual/basic_concepts/the_lister/layouts.md) and [styles](/directory-opus/manual/basic_concepts/the_lister/styles.md).

More:

[Drive Buttons Configuration](/directory-opus/manual/customize/creating_your_own_buttons/editing_the_toolbar/dynamic_buttons/drive_buttons_configuration.md)


---

# 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://chaoses-ib.gitbook.io/directory-opus/manual/customize/creating_your_own_buttons/editing_the_toolbar/dynamic_buttons.md?ask=<question>&goal=<user_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.