> For the complete documentation index, see [llms.txt](https://docs.aviator.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aviator.co/aviator-cli/faqs-and-troubleshooting/working-with-aviator.md).

# Working with Aviator CLI

The Stacked PRs CLI is free and open-source, that means you can use the CLI with no usage caps without creating an Aviator account. Simply follow the [<mark style="color:blue;">installation instructions</mark>](/aviator-cli/installation.md) to set up the CLI locally.

## MergeQueue

[<mark style="color:blue;">Aviator MergeQueue</mark>](/mergequeue.md) is a powerful merge-based automated workflow for pull requests in your GitHub repository and keeps your primary branch passing. Although completely optional, using the Aviator MergeQueue along with the stacked PRs CLI can significantly improve the developer experience for [<mark style="color:blue;">merging and updating the PRs</mark>](https://docs.aviator.co/mergequeue/how-to-guides/merging-stacked-prs).

To enable MergeQueue with Stacked PRs, create an Aviator account, [<mark style="color:blue;">configure MergeQueue mode</mark>](/mergequeue/quick-setup.md), and [<mark style="color:blue;">set up the Aviator user access token</mark>](/aviator-cli/how-to-guides/create-a-user-access-token.md#aviator-user-access-token) in your Stacked PRs CLI config.

### Chrome Extension

[<mark style="color:blue;">Chrome Extension</mark>](/aviator-chrome-extension.md) is also a great way to visualize your stack from within GitHub pull request page.

<figure><img src="/files/Pm1SBJ2G1jAxiYVDASgC" alt=""><figcaption><p>Chrome Extension view</p></figcaption></figure>


---

# 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://docs.aviator.co/aviator-cli/faqs-and-troubleshooting/working-with-aviator.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.