> 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/getting-started/arguments/prompt-and-session-arguments.md).

# Prompt and Session Arguments

Prompt flags apply to one prompt; session tags run after the whole flow completes or is cancelled.

| Argument             | Syntax                                | Scope   | Description                                          |
| -------------------- | ------------------------------------- | ------- | ---------------------------------------------------- |
| Chat                 | `<Display>`                           | Prompt  | Captures the next chat message.                      |
| Anvil                | `<a:Display>`                         | Prompt  | Opens an Anvil input.                                |
| Sign                 | `<s:Display>`                         | Prompt  | Opens a Sign input.                                  |
| Player UI            | `<p:Display>` or `<p:filter:Display>` | Prompt  | Selects an online player.                            |
| Dialog               | `<d:filter:Display>`                  | Prompt  | Opens a native Paper dialog.                         |
| Preset               | `<@id>`                               | Prompt  | Loads a prompt from `presets.json`.                  |
| Disable sanitation   | `-ds`                                 | Prompt  | Preserves session input from the normal sanitizer.   |
| Validation           | `-iv:<alias>`                         | Prompt  | Applies a configured validator.                      |
| Integer              | `-int`                                | Prompt  | Requires a signed 32-bit integer.                    |
| Nonblank string      | `-str`                                | Prompt  | Rejects blank input.                                 |
| Title display        | `-t` or `-t:Main\|Sub\|ticks`         | Prompt  | Shows an Adventure title before the prompt.          |
| On completion        | `<!command>`                          | Session | Runs an inline post-command after success.           |
| On cancellation      | `<!!command>`                         | Session | Runs an inline post-command after cancellation.      |
| Delayed post-command | `<!:ticks command>`                   | Session | Delays an inline post-command.                       |
| Post-command preset  | `<!@id>`                              | Session | Loads a post-command definition from `presets.json`. |

Multiple prompt flags can be combined as whitespace-delimited tokens. Compound Dialog flags apply to the whole block, and every input row consumes its own answer index.

```
/example <d:choice[set,add]:Action && d:num[0,24]:Value -iv:request -t:"Request"> <!audit {0} {1} @console>
```


---

# 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/getting-started/arguments/prompt-and-session-arguments.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.