Docs / Work tools
GitHub
Install the Pangea GitHub App to let agents read repositories and work on pull requests, issues and checks.
Pangea connects to GitHub through the Pangea GitHub App. Access covers only the repositories you pick, and there is no personal access token to manage. Once connected, the agent can work with pull requests, issues, checks, commits and repository contents.
Connect
1. Start the install
As a team Administrator, open Connectors, find GitHub and click Add, then click Install GitHub App. Your browser opens GitHub's installation screen.
2. Choose what it can access
Pick the organization or personal account, then choose All repositories or a specific set. GitHub controls exactly what the app can see.
3. Confirm the team
GitHub asks you to authorize the app so Pangea can check that you have access to that installation. Pangea then shows a Connect GitHub to Pangea page that names your Pangea team and the GitHub account. Click Connect only if you started from that team.
4. Return to Pangea
The browser hands you back to the Mac app through a pangea:// link, and the dialog closes by itself. There is nothing to copy and paste.
If nothing happens after you approve, check that your browser allowed the pop-up and that pangea:// links open the Pangea app.
What the app can access
The Pangea GitHub App asks for these repository permissions:
| Permission | Access |
|---|---|
| Metadata | Read |
| Contents | Read |
| Pull requests | Read and write |
| Issues | Read and write |
| Checks | Read |
In the Pangea app
Browse the repositories you granted, with their pull requests, commits and contents, without leaving Pangea.
What the agent can do for you
With code and CI visible, the agent can connect what is deployed to where it came from. Ask it things like:
- "Did the last release pass its checks, and what changed in it?" It reads the checks and the commits behind them.
- "The
checkoutservice started failing after yesterday's release. What changed?" It matches the incident window with merged pull requests and reads the diff. - "Open an issue summarizing this incident." Name the repository and what the issue should say before it publishes.
Permissions and authorization
Team Administrators connect and remove this connection. They can limit it with a member allow-list. Select the connection for the conversation before you ask the agent to use it. GitHub permissions stay the outer limit, whatever the prompt or permission mode.
Each action follows Auto Mode and Full Access. Significant cloud infrastructure work uses plans. A ticket, a repository write or a routine API call does not create a plan by itself. If you want to review changes before they are published, say so in your request.
Good to know
- Repository selection lives on GitHub, not in Pangea. Widen or narrow it in your organization's Installed GitHub Apps settings, and Pangea picks up the change.
- The connection is an app installation, not a personal token. It is not tied to one person's GitHub account and keeps working when people leave the organization.
Use your own GitHub identity
For commits, pull requests and comments authored by you, connect GitHub under Settings → Personal Credentials and select it for the conversation. This is separate from the team's GitHub App connection. Check which login the agent is acting as before a write. Your personal connection is not shared with other people in the session.
Ask the agent to use signed commits when the repository requires them. A token used to push does not sign a commit by itself. A pull request linked to its session can receive later events, but a link alone does not prove that CI passed or that a review is done.