Connect GitHub

The GitHub connector lets Treasure AI Studio agents work with your GitHub repositories during a chat — cloning code, reading and editing files, opening and reviewing pull requests, and managing issues on your behalf. The agent uses the gh CLI and git over HTTPS inside its sandbox, authenticated by your connection. Like the Treasure Data connector, there is no OAuth application to create on the vendor side.

Setup has three parts, each done by a different role: a Studio administrator enables the connector, someone with rights on a GitHub account or organization installs the Treasure AI GitHub App on the repositories the agent may access, and each user authorizes their own connection. The middle part happens entirely on GitHub's side and is not tied to your Studio account — see GitHub App Installations Are Separate From Your Studio Account.

Enable the GitHub connector, install the Treasure AI GitHub App on the repositories the agent may access, and authorize a connection so the agent can work with your code, issues, and pull requests. You'll also see exactly which actions the GitHub App is permitted to perform.

• Account administrator privileges in Treasure AI Studio — needed for Step 1 only (enabling the connector)
• Rights on GitHub to install a GitHub App where you want the agent to work — needed for Step 2 only. You can install on a personal account you own; installing on an organization requires organization owner rights. This is a GitHub permission and has nothing to do with your Studio role.

Because Treasure AI manages the GitHub App and its OAuth client, there is nothing to register on the vendor side and no client ID or secret to enter — enabling the connector just makes GitHub available on the Connections tab.

1. In Treasure AI Studio, open Settings → Connector Settings (under Organization).
2. Click Add Connector (or Add your first connector) and choose GitHub.
3. The GitHub connector has no configuration fields to fill in — click Save to add it.
4. Make sure the connector is enabled so users can authorize connections to it. GitHub then appears under Available on every user's Connections tab.

The Setup Guide panel beside the form links to the GitHub App installation page. The panel itself belongs to the add-connector form and appears only while you are adding the connector — but the link it carries does not disappear with it. After you click Save, the saved connector row offers an expander (which shows the connector's stored configuration fields, of which GitHub has none), an enable toggle, and a delete button.

Below those, the row shows a reminder for each domain the connector needs to reach and, at the bottom, an always-visible note linking to the GitHub App installation page:

The reminders are listed for every connector that declares egress domains, and stay visible whether or not your network policy already allows them — they tell you what the connector requires, not that something is misconfigured. The note below them repeats the installation-page link, so you can reach it at any time — not only while adding the connector. (It's a public GitHub URL in any case, given in full in Step 2.)

Installing the App is what actually grants access: the agent can only reach repositories where the Treasure AI GitHub App is installed. This is the control that scopes what the agent can touch — install it only on the repositories you want the agent to work with.

The App is published on GitHub as Treasure AI GitHub Integration, owned by the treasure-data organization:

1. Open the installation page. You must be signed in to GitHub.
2. Choose the organization or personal account to install into. GitHub lists only the accounts where you are allowed to install an App — your own personal account, plus any organization you have install rights in. If the organization you need is missing, ask an organization owner to install it (GitHub also lets organization members send an installation request to the owners).

3. Select All repositories or Only select repositories, and pick the repositories you want the agent to access. GitHub's own notes on this screen are worth reading: All repositories applies to all current and future repositories owned by that account, and either choice "also includes public repositories (read-only)".
4. Review the permissions (see What the GitHub App Can Access below) and click Install. The screen also lists User permissions — the access requested from each user individually when they authorize their connection in Step 3.

You can repeat this for as many accounts and organizations as you need — see Installation Examples.

To change which repositories the agent can reach later, or to remove access entirely, go to the installation's Configure page on GitHub: Your organizations → Settings → GitHub Apps for an organization, or Settings → Applications → Installed GitHub Apps for a personal account. Nothing needs to change in Studio when you do.

With the connector enabled and the App installed, each user who wants the agent to access GitHub authorizes their own connection. You can do this ahead of time from Settings, or on demand from a chat.

1. Open Settings → Connections.
2. Under Available, find GitHub and click Connect.

3. Sign in to GitHub in the popup and approve the requested access. GitHub's authorization screen names the exact account you are authorizing as — Verify your GitHub identity (your-handle) — and lists the rest of what it grants: knowing which resources you can access, acting on your behalf, and read access to your email addresses. Approving it returns you to Studio and closes the popup.

4. When the popup closes, GitHub appears in your connected list with the date you connected it, and a delete (trash) icon beside it.

To remove the connection later, click that delete (trash) icon. Deleting it removes the authorization stored in Studio; it does not uninstall the GitHub App.

The agent authorizes as you and acts with your GitHub identity — commits it creates are attributed to your account. Crucially, the agent can reach a repository only when both conditions hold: the GitHub App is installed on that repository (Step 2), and your own GitHub account has access to it. In other words, the agent's reach is the intersection of the App's installed repositories and your personal access — never more than you could reach yourself.

One connection covers every account and organization where the App is installed. You authorize GitHub once, and the agent can then work across all of those repositories that you personally have access to — you don't create a separate connection per organization.

Once connected, ask the agent to work with your repositories — for example, to clone a repository, summarize recent changes, open a pull request, review a PR, or triage issues. The agent runs gh and git commands with your connection automatically; no extra configuration is needed in the chat. The gh CLI is pre-authenticated inside the sandbox, so the agent never runs gh auth login.

A GitHub App is always installed into a GitHub account — either a personal account or an organization. That installation is the object GitHub creates; what it grants is then scoped to repositories inside that account, either All repositories or a list you select. So the target of an install is an account, while the access it hands out is per repository. It is not installed into Treasure AI Studio, and GitHub has no concept of your Studio account when you install it. This trips people up because the link to the installation page appears inside Studio, which makes it look like the two are being paired.

They are not. Reaching the installation page from a Studio account does not associate that GitHub account with that Studio account, and Treasure AI stores no mapping between them. A single App — Treasure AI GitHub Integration — serves every Studio account in every region. One installation is therefore not bound to whoever created it: any Studio user who authorizes with a GitHub account that can reach those repositories gets the same access.

What actually controls access is this pair of conditions: the Treasure AI GitHub App must be installed on the repository (Step 2), and the person authorizing the connection must have access to that repository with their own GitHub account (Step 3). Because the second condition always applies, a shared installation can never give anyone more than they already had on GitHub.

The practical consequences:

These are the three situations that come up most often when installing the Treasure AI GitHub Integration App, and what each one requires.

Your team's repositories live in a company GitHub organization, and you want the agent available to everyone who works in them.

1. A Studio administrator enables the GitHub connector once (Step 1).
2. A GitHub organization owner installs the App on that organization, choosing Only select repositories and picking the repositories agents may work with (Step 2).
3. Each team member authorizes their own connection (Step 3). No further GitHub-side action is needed per person.

Every member's agent is then scoped to the intersection of the selected repositories and that member's own access, so someone with read-only access to a repository cannot have the agent push to it.

If you are a member of the organization but not an owner, the same page turns into a request instead: the button reads Request rather than Install, and GitHub sends the request to the organization's owners to approve.

You already work with your company's organization, and now you also want the agent to work with repositories somewhere else — your own personal account, a second organization, or a client's organization.

1. Open the installation page again and install the App into the additional account or organization. You need install rights there; for your own personal account, that's just you.
2. Nothing changes in Studio — no new connector, and no second connection. Your existing GitHub connection already covers every account where the App is installed.

This is the case that most clearly shows the separation: no Studio administrator is involved, and no Studio setting records the new organization.

The App is already installed, but a repository the agent needs wasn't included — or you want to remove one.

1. On GitHub, open the installation's Configure page: Your organizations → Settings → GitHub Apps → Treasure AI GitHub Integration for an organization, or Settings → Applications → Installed GitHub Apps for a personal account.
2. Under Repository access, add or remove repositories, then Save.
3. Nothing changes in Studio, and you don't re-authorize your connection — the same connection now covers the updated repository selection.

This page is also where GitHub restates the access rule itself: under How access is scoped, it describes effective access as the intersection of the repositories where the integration is installed and the repositories the authorizing user can reach, and states that the agent cannot access repositories outside that intersection.

Uninstalling from that page removes agent access to all of the account's repositories at once. It leaves your Studio connection in place, so delete the connection too if you want to remove the stored authorization as well.

The Treasure AI GitHub App requests a fixed set of permissions — you cannot broaden or narrow them per install. It is scoped to what an agent needs to work with code and collaborate on issues and pull requests, and deliberately excludes administrative and secret-management capabilities. The tables below list every permission the App holds.

For safety, the App holds no access to the most sensitive capabilities, including:

• Secrets and Dependabot secrets — it never reads or writes repository or Actions secrets.
• Workflows — it cannot create or modify GitHub Actions workflow definitions (it can only re-run existing ones via the Actions permission).
• Administration — it cannot change repository settings, collaborators, or branch protection.
• Codespaces and Copilot agent settings — out of scope for the agent.
• Secret scanning bypass and dismissal requests, and attestations.

• Connections — The general connection model and administrator controls
• Connect Treasure Data CDP — Enable the connector and authorize a Treasure Data connection
• Skills & Marketplace — How skills give the agent domain expertise
• Security Overview — How access control works in Studio