Skip to main content
Connect GitHub repositories so Loop can move from a failing trace to the code that explains it, with source code and production evidence in the same investigation. Ask Loop to:
  • Find the tool implementation or prompt logic behind an unexpected response.
  • Compare failing and successful traces with the code to identify a likely cause.
  • Suggest a targeted fix and a regression test based on the failure.
The integration provides read-only GitHub access: Loop can clone and fetch repositories, but cannot push changes or open pull requests.
The GitHub integration is in private preview, available to a limited set of customers. To request access, contact Braintrust.

​
Connect GitHub

You need the Manage settings organization permission to connect GitHub and set the organization’s default connection. Organization owners have this permission by default. You also need to own the GitHub account or be an administrator of the GitHub organization you’re connecting.
1

Connect an installation

Go to Settings > Integrations and click Connect GitHub.Authorize access in GitHub, then choose an existing installation and click Connect, or click Install in a new organization. When installing the Braintrust GitHub App, select the repositories you want it to access.Back in Braintrust, click Show repositories to check the installation’s repository access.
2

Set the organization default

In organization Integrations settings, click Set as default on the installation you want Loop to use. Projects without an explicit connection inherit this default. Existing explicit project connections take precedence over the organization default.
3

Use the code in Loop

Start a new Loop thread in the project and ask a question that combines traces with source code:
Loop automatically clones up to five authorized repositories when it creates the sandbox. Each checkout starts with the latest commit on the default branch, under github/<owner>/<repo> in the sandbox working directory. Ask Loop to clone another authorized repository when you need it.

​
Repository access and security

GitHub read access uses a short-lived token covering every repository available to the connected GitHub App installation. For Git operations, the egress proxy supplies that token only for repositories selected for Loop and only for cloning or fetching. The proxy does not authorize Git pushes. GitHub tokens are not passed to the model or stored in the sandbox. The sandbox receives ephemeral proxy credentials, while repository source files remain in the sandbox for Loop to inspect.
Connecting a repository makes its code available through Loop to people with read access to the Braintrust project. Access uses the Braintrust GitHub App installation, not each person’s GitHub account. Choose repositories and project membership accordingly.

​
Manage connections

In organization Integrations settings, click Set as default on another installation to change the default, or Remove default to stop providing a default connection.These changes affect projects that inherit the organization default. Existing explicit project connections remain unchanged.
Changing or removing the default does not erase repository files already cloned into an existing sandbox. See sandbox lifecycle for how sandbox files are retained.
Change the repositories available to the Braintrust GitHub App in GitHub’s installation settings. In Braintrust’s organization Integrations settings, use Show repositories to check access or Disconnect to remove the connection.
Disconnecting an installation removes access through it for every Braintrust project that uses it. Projects explicitly connected to that installation do not fall back to the organization default. Disconnecting does not delete existing sandbox checkouts.
Check that the installation is active, the repository appears under Show repositories, and the installation is marked as the organization default. An existing explicit project connection takes precedence over that default. If the repository is authorized but was not automatically cloned, ask Loop to clone it by its owner/repo name.Start a new thread after changing the connection so Loop creates a new sandbox and prepares the checkouts. A failed checkout does not prevent the rest of Loop from working. Ask Loop to check whether the repository is available before continuing a source-code task.

​
Limitations

  • Braintrust-hosted deployments only. This integration is not yet available on self-hosted deployments.
  • Read-only GitHub access. Loop can clone and fetch repositories, inspect code, and suggest fixes. It cannot push changes or open pull requests through this integration. Apply and submit suggested changes through your own development workflow.
  • Up to five automatic checkouts. Loop automatically clones the first five authorized repositories, ordered by GitHub repository ID. However, you can ask Loop to clone additional authorized repositories.
  • Shallow checkouts. Each checkout starts with the latest default-branch commit, without tags or earlier history. Ask Loop to fetch additional history or updates when needed.

​
Next steps