> 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/verify/setting-up-your-team.md).

# Setting up your team

Getting a team onto Verify has two halves. An admin turns on agent hooks for everyone working in a given repository. Then each engineer connects their GitHub account and sets up the CLI and the Aviator skill on their own machine, which is covered in [Setting up your machine](/verify/setting-up-your-machine.md).

This page is the admin half.

**Before you start:**

* The repository needs to be connected to Verify. See [Connect a repository](/verify/how-to-guides/connect-a-repository.md).
* Everyone who will use Verify needs an invite to your company's Aviator workspace.

## 1. Install the CLI

```bash
brew trust aviator-co/tap
brew install aviator-co/tap/aviator
```

`brew trust` is needed on Homebrew 6 and later, which only loads third-party taps you've trusted. On Linux, install the `.deb` or `.rpm` from the [releases page](https://github.com/aviator-co/aviator-cli/releases).

## 2. Run `aviator init`

`cd` to the repository you're setting up, then:

```bash
aviator init
```

If you aren't signed in yet, it offers to sign you in first, which opens your browser and stores the session in your OS keychain.

<figure><img src="https://273246003-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOAPqUQVbLbsfI5YESl32%2Fuploads%2Fgit-blob-77d65ab99a7d5a5c6409377eb13f12d957947330%2Fverify-init-sign-in.png?alt=media" alt="aviator init in a terminal, explaining that it sets up coding agents to capture intent, and prompting Sign in to Aviator? with Yes selected"><figcaption><p><code>init</code> offers a sign-in when it can't find credentials</p></figcaption></figure>

Then it asks which agents to set up. Select every agent used by your team in this repository, not just the one you use. The configuration is committed, so it covers your whole team.

<figure><img src="https://273246003-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOAPqUQVbLbsfI5YESl32%2Fuploads%2Fgit-blob-52de6f762cd4d1f69bb2f91818346e5cacad3ce6%2Fverify-init-agents.png?alt=media" alt="Terminal output confirming the sign-in and that the session is stored in the system keychain, followed by a Set up which agents? prompt with Claude Code and Codex both checked"><figcaption><p>Select every agent used in the repository</p></figcaption></figure>

## 3. Commit the hooks

`init` writes `.claude/settings.json` for Claude Code and `.codex/hooks.json` for Codex, then prints the git commands to put them on a branch. Run those and open the PR. Merging it turns the hooks on for everyone.

Support for other agents is coming. If your team uses a different one, email <howto@aviator.co> and we'll send you the manual setup steps.

Every agent session in the repo then carries a standing instruction to capture intent and acceptance criteria before a PR, plus reminders at commit and PR time. None of it blocks. A teammate missing the CLI or a sign-in still commits and opens pull requests exactly as before, gets told what's missing at their next session start, and their changes simply don't reach Verify. See [Set up agent hooks](/verify/how-to-guides/set-up-agent-hooks.md) for the detail.

## 4. Send your team the setup steps

Everyone working in the repository sets up their own machine: [Setting up your machine](/verify/setting-up-your-machine.md).

## See also

* [Setting up your machine](/verify/setting-up-your-machine.md), the half your team does
* [Set up agent hooks](/verify/how-to-guides/set-up-agent-hooks.md), what each hook does and how to remove them
* [Connect a repository](/verify/how-to-guides/connect-a-repository.md)
* [Aviator CLI](/verify/reference/cli.md), the full command surface
* [Setting up org invariants](/verify/setting-up-org-invariants.md), the rules that apply to every change automatically


---

# 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/verify/setting-up-your-team.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.