> For the complete documentation index, see [llms.txt](https://yagsl.yassrobotics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://yagsl.yassrobotics.com/readme.md).

# Welcome to YAGSL

Brought to you by Yet Another Generic Swerve Library (YAGSL)

<figure><img src="https://567506766-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F754c0Fpq8fBi6k4ByS1k%2Fuploads%2Fgit-blob-aa613fd0fa12ea482c7e410ce1d910443d569c2b%2FYAGSL.png?alt=media" alt=""><figcaption></figcaption></figure>

YAGSL is a swerve library developed by current and former BroncBotz mentors for all FRC teams. It reads a JSON description of your swerve drive and builds a [YAMS](https://yams.yamgen.com/) `SwerveDrive` from it: describe your hardware once at [**config.yagsl.com**](https://config.yagsl.com), and drive. See [What is YAGSL?](https://yagsl.yassrobotics.com/how-it-works/what-is-yagsl.md) for how the pieces fit together.

{% hint style="success" %}
YAGSL 2027 is built on WPILib 2027 (`2027_alpha7`, Java 25) and runs on the SystemCore. It supports both WPILib Commands v2 and Commands v3, each with its own vendordep. See the [Changelog](https://yagsl.yassrobotics.com/upgrading/changelog.md) for what changed in the 2027 port.
{% endhint %}

## Where to start

| If you...                                                      | Go to                                                                                                                                                    |
| -------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| are setting up YAGSL for the first time                        | [**Your first swerve robot**](https://yagsl.yassrobotics.com/get-started/tutorial.md), seven steps from a bare WPILib project to a driving robot         |
| have a robot that isn't driving right                          | [**Find your problem**](https://yagsl.yassrobotics.com/fix-a-problem/fix-a-problem.md), which matches what your robot is doing to the page that fixes it |
| have a driving robot and want to do more with it               | [**Tune and extend**](https://yagsl.yassrobotics.com/tune-and-extend/how-to.md): PIDF tuning, drive to a pose, PathPlanner and more                      |
| are upgrading a 2026 project or a config from before 2026.8.05 | [**Upgrade to YAGSL 2027**](https://yagsl.yassrobotics.com/upgrading/schema-changes.md), before you do anything else                                     |
| need an exact JSON field, device type or API                   | [**Reference**](https://yagsl.yassrobotics.com/reference/reference.md)                                                                                   |

{% embed url="<https://www.youtube.com/watch?v=4Tcyn_oj_G0&list=PLdhNPDifsCMLLe5pZoyHGXrMMVxNpJOxP>" %}

## Install

Install **exactly one** YAGSL vendordep, matching the WPILib command framework your robot uses (they conflict with each other). In WPILib's VS Code, open the **WPILib Vendor Dependencies** panel and install **Yet Another Generic Swerve Library (Commands v2)** or **(Commands v3)**.

[Install YAGSL](https://yagsl.yassrobotics.com/get-started/02-install-yagsl.md) covers the YAMS vendordep each one requires, installing from a URL instead, updating to beta versions, and the vendor libraries for your hardware.

{% hint style="warning" %}
The old `https://yet-another-software-suite.github.io/YAGSL/...` vendordep and maven URLs are stale. Remove the old `yagsl.json` from your `vendordeps` folder and install YAGSL again.
{% endhint %}

{% embed url="<https://datawrapper.dwcdn.net/ZVxvE/13/>" %}

## Our philosophy

Your program does not revolve around your swerve drive. Your constants file doesn't have to take 10 minutes to find the right option. Different robots should be able to work with the same code: swap the `swerve/` config directory and the same subsystem code drives a different 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://yagsl.yassrobotics.com/readme.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.
