> For the complete documentation index, see [llms.txt](https://docs.raidrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.raidrobotics.org/raidsystems/robot/controls.md).

# Controls

**Robot › Controls** shows every controller in the robot code and what each button does.

## Read a controller

Pick a controller. The drawing shows its face as the driver holds it: lit buttons do something. Click a button to find its bindings, which are highlighted in the list. Switch to the code view to see each binding's code.

## Describe and approve buttons

Every binding needs a plain description the drive team has approved.

1. A programmer, mentor or admin clicks **Draft Button Mappings with AI**. Claude reads the robot code and drafts a description and a short name (3 words at most) for every binding that doesn't have a draft yet. The button is disabled when nothing is waiting, because each run costs money.
2. A draft shows as **Drafted by Claude** while the binding is unreviewed. Fix anything that's wrong.
3. Someone on the drive team clicks **Approve**.

A binding whose code changes goes back to unreviewed after the next [code sync](https://docs.raidrobotics.org/raidsystems/robot/overview-and-code-sync.md), and gets a new draft on the next run.

Add **Notes** for anything the code can't see, like remapped paddles.


---

# 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://docs.raidrobotics.org/raidsystems/robot/controls.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.
