> 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/features/console-delegate.md).

# Console Delegate

Console Delegate lets the server console ask one player for input and dispatch the completed command as console.

```
/consoledelegate <target> <command...>
/cd <target> <command...>
```

* `target` accepts a player name or a single-target Minecraft selector such as `@p`. Multi-target selectors such as `@a` are rejected by the command's singular player argument.
* `command...` is a greedy command string and may start with `/`.
* `%target_player%` is replaced with the target player's name.
* The sender must be the console and have `promptpaper.consoledelegate`.

When `Enable-Permission` is enabled and the delegated command contains prompt tags, the target player must also have `promptpaper.use`. A rejected prompt flow is not dispatched literally. This target-side gate does not block a direct delegated string with no prompt tags.

## Example

```
/consoledelegate CyR1en gamemode <What gamemode?> %target_player%
```

If CyR1en answers `creative`, console dispatches:

```
gamemode creative CyR1en
```

If the delegated string contains no prompt tags, it is dispatched immediately as console. An unresolved preset or another rejected tag form is not dispatched literally.

## Post-commands

An inline post-command without an executor marker inherits the main command's console context:

```
/cd CyR1en gamemode <Gamemode?> %target_player% <!broadcast %target_player% selected {0}>
```

Use `@player` to force an inline post-command to run as the target player. Use `@console` to be explicit. Preset post-commands do not inherit: their `execute_as` property is authoritative.

{% hint style="danger" %}
Console Delegate gives player-supplied answers to a console command. Keep the command template fixed, validate untrusted input, and grant access only to trusted console automation.
{% endhint %}


---

# 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://cyr1en.gitbook.io/commandprompter/features/console-delegate.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.