> For the complete documentation index, see [llms.txt](https://sheets.bed.codes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sheets.bed.codes/features/editor.md).

# Editor & Input

Sheets provides interactive ways to edit and interact with menus.

### 1. Chest Edit Mode (Java Only)

Chest Edit Mode allows you to visually edit your menus in-game.

#### How to Open

* Run [`/sheets edit <menu> chest`](/getting-started/commands.md#management-commands).
* Alternatively, open the edit menu with `/sheets edit` and right-click on the sheet you want to edit.

#### Functionality

1. Once in Chest Edit Mode, you can drag and drop items from your inventory into the menu or rearrange existing items.
2. Closing the inventory will automatically save the new layout to the menu's YAML file as `buttons`.
3. Each item in the menu will be saved with its material, name, and lore.

### 2. Anvil Input

Anvil menus can be used to capture text input from players.

#### Usage via Actions

Define an [`input` action](/features/actions.md#input-action) in your YAML:

```yaml
actions:
  - input:
      title: "Enter text"
      command: "say you entered {text}"
```

#### Dynamic Anvil Menus

If you specify a title in the `input` action that doesn't correspond to a pre-defined menu, Sheets will dynamically create an Anvil menu with that title.

#### Real-time Updates

Anvil menus refresh every second (20 ticks), allowing placeholders like `{text}` to update in item names and lore as the player types.

#### Confirmation Button

Slot 2 in an Anvil menu is typically used as the confirmation button. The action defined in the `input` command will be executed when this button is clicked.


---

# 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://sheets.bed.codes/features/editor.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.