> ## Documentation Index
> Fetch the complete documentation index at: https://docs.remyx.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect GitHub

> Connect a repository to Remyx and manage its GitHub App installation.

Connect the repositories where you want to review changes or run validations.

## For Validate

1. Open [Connectors in Studio](https://studio.remyx.ai/connectors).
2. Install the Remyx GitHub App on the repositories you select.
3. Return to Studio and connect or claim the installation if prompted.
4. Confirm that Validations are enabled for that installation.

To start a validation, comment `@remyx-ai validate` on an open pull request in the connected repository.

[Read the Validate guide](https://docs.remyx.ai/platform/agents/validate.md)

## For Outrider

Use [Studio Quickstart](https://studio.remyx.ai/start) to authorize GitHub, choose a repository, and install the Outrider workflow.

The Quickstart's GitHub connection and repository setup have distinct permission steps. Follow the prompts in Studio rather than installing a workflow manually.

## Permissions

The exact permissions, installation-claim rules, and repository controls are documented below.

**What it feeds:** the ranking baseline (every merge and revert re-weights the candidate pool), the write path for everything agents author, and the mention surface for [Validate](https://docs.remyx.ai/platform/agents/validate.md).

**Setup:**

1. Click **Connect** on the GitHub card.
2. Install the **Remyx GitHub App** on your organization or account.
3. Select the repositories to grant access to.

> [!NOTE]
>
> The connector is a **GitHub App**, not a plain OAuth grant. Remyx authenticates as the App and mints short-lived, repo-scoped tokens on demand; the App's private key never leaves the Remyx engine. The base token covers `contents`, `pull-requests`, `issues`, and `workflow` (needed to install the agent workflow), and permissions like `discussions:write` are layered on only when your installation actually granted them.

### The `remyx-ai[bot]` identity

Because the connector is a GitHub App, everything Remyx does on your repos is authored by **remyx-ai\[bot]**: setup PRs, draft PRs, Issues, and Validate's commits to a PR branch. Never as you, so it's clear at a glance which artifacts an agent originated. Commits show as **Verified**.

The bot answers `@remyx-ai` mentions in two ways, and they have different reach:

* **Research questions** on a PR or Issue an agent opened get a grounded, read-only reply. See [Briefs](https://docs.remyx.ai/platform/discover/briefs.md#the-remyx-bot).
* **`@remyx-ai validate`** works on **any** PR in a repo the App covers, whoever opened it, and it does write: it commits a proposed test, its environment and the executed notebook to the PR branch. Nothing lands on the default branch. See [Validate](https://docs.remyx.ai/platform/agents/validate.md).

### Installations

Below the card, one row per App installation Remyx can see:

| Column | Meaning |
| - | - |
| **Account** | The GitHub user or organization the App is installed on, and its repository selection. |
| **Owner** | The Remyx account that claimed it. Validate gates, charges and attributes runs to this account. |
| **Claim** | Shown when nobody has claimed the installation. The claimer must be able to reach it through their own GitHub authorization. An installation another account owns is not transferred. |
| **Validations** | The per-installation switch, on by default. Off, the bot replies that validations are turned off for the repo and does nothing. A legacy Outrider agent's own toggle under Agents → repo → Validations is honoured alongside it. |

Connecting GitHub from Studio claims the installations you can reach. The API is `GET /github/app/installations`, `PATCH /github/app/installations/<id> {validations_enabled}` and `POST /github/app/installations/<id>/claim` (`github:write`).

> [!NOTE]
>
> The in-app [Quickstart](https://docs.remyx.ai/quickstart.md) uses a repo-scoped OAuth connection (it needs fork rights for the demo repo); agent setup outside the quickstart runs on the App. If both exist, the App is preferred.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.