> For the complete documentation index, see [llms.txt](https://cyr1en.gitbook.io/commandprompter/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cyr1en.gitbook.io/commandprompter/configuration/prompts-configuration.md).

# Prompts Configuration

`prompt-config.yml` contains the UI defaults for Chat, Player, Anvil, Sign, Dialog, and Confirmation prompts, plus input-validation definitions.

The file is generated in `plugins/CommandPrompterPaper/` on first start. Edit it while the server is stopped or use `/cmdp reload` after saving changes. Reload cancels active prompt sessions.

{% hint style="info" %}
The `screen-mappings` section is honored during inline prompt routing. A configured key maps to `CHAT`, `ANVIL`, `SIGN`, `DIALOG`, `PLAYER`, `CONFIRMATION`, or `ITEM`. Built-in aliases remain reserved: the empty Chat key, `a`/`anvil`, `s`/`sign`, `p`/`player`, `d`/`dialog`, `c`/`confirm`/`confirmation`, and `i`/`item`. Other keys must be mapped or registered by a [custom screen provider](/commandprompter/developers/custom-screens.md); unresolved keys fail closed instead of falling back to Chat.
{% endhint %}

Continue with the page for the UI you want to configure:

* [Chat Prompt](/commandprompter/configuration/prompts-configuration/chat-prompt.md)
* [Player UI](/commandprompter/configuration/prompts-configuration/player-ui.md)
* [Anvil UI](/commandprompter/configuration/prompts-configuration/anvil-ui.md)
* [Sign UI](/commandprompter/configuration/prompts-configuration/sign-ui.md)
* [Dialog UI](/commandprompter/configuration/prompts-configuration/dialog-ui.md)
* [Confirmation Prompt](/commandprompter/prompts/confirmation-prompt.md#configuration)
* [Item Selector Prompt](/commandprompter/prompts/item-selector-prompt.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 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://cyr1en.gitbook.io/commandprompter/configuration/prompts-configuration.md?ask=<question>&goal=<endgoal>
```

`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.