> 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/programming/getting-started/tools.md).

# Tools

The software a controls member needs, and what each tool is for. The [Robot Template install guide](https://docs.raidrobotics.org/robot-template/getting-started/install-and-build.md) has the exact versions for this season.

| Tool                           | What it's for                                                                                                                               |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------- |
| WPILib (with VS Code and Java) | Writing, building and deploying robot code. The WPILib installer also installs VS Code and the right JDK, so don't install Java separately. |
| Git and GitHub                 | Version control for all team code, in the [Team4469](https://github.com/Team4469) organization. Use git or GitHub Desktop.                  |
| FRC Driver Station             | Enabling and driving the robot from a laptop.                                                                                               |
| roboRIO Imaging Tool           | Setting up a roboRIO for the season.                                                                                                        |
| Phoenix Tuner X                | Finding, configuring and testing CTRE devices on CAN.                                                                                       |
| Elastic                        | A dashboard for live values while the robot runs.                                                                                           |
| AdvantageScope                 | Viewing logs and live data, including the swerve and field views.                                                                           |

## Set up a laptop

1. Install WPILib for this season from [docs.wpilib.org](https://docs.wpilib.org).
2. Install Git or GitHub Desktop and sign in to GitHub. Ask a mentor to add you to the Team4469 organization.
3. Clone the season's robot code and build it, following [Install and build](https://docs.raidrobotics.org/robot-template/getting-started/install-and-build.md).
4. Run it in the [simulator](https://docs.raidrobotics.org/robot-template/getting-started/simulator.md) before touching the real robot.


---

# 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/programming/getting-started/tools.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.
