Docs / Work tools
GitLab
Connect gitlab.com or your own GitLab instance over OAuth to work with merge requests, pipelines and code.
Pangea connects to GitLab over OAuth. gitlab.com works with Pangea's own OAuth app. Your own GitLab instance needs a one-time OAuth application that you create there. Once connected, the agent can work with merge requests, pipelines, issues and repository contents.
Connect gitlab.com
1. Start the connection
As a team Administrator, open Connectors, find GitLab and click Add. Keep the GitLab host as https://gitlab.com.
2. Choose access
Read projects is always on. It covers projects, repositories, merge requests and pipelines. Turn on the extras you need:
| Option | What it adds | GitLab scope |
|---|---|---|
| Read projects (always on) | Read projects, code, MRs and pipelines | read_api, read_user, read_repository |
| Push branches | Clone, commit and push branches | write_repository |
| Manage merge requests | Open MRs, update metadata, post comments | api |
3. Authorize and return
Click Authorize GitLab. Approve the request on GitLab's consent screen. GitLab sends you back to the Mac app through a pangea://gitlab-callback link, and the connection completes.
Connect your own GitLab instance
1. Create an OAuth application on your GitLab
In your GitLab instance, open Admin Area → Applications, or create a group or user application. Set:
- Redirect URI:
https://api.pangea.build/gitlab-app/setup - Scopes: the ones for the access you plan to grant, from the table above. Include
read_api,read_userandread_repository.
Save it and copy the Application ID and Secret.
2. Enter the host and credentials in Pangea
In the GitLab dialog, set the GitLab host to your instance URL, for example https://gitlab.example.com. Click Show OAuth app settings and paste the OAuth application ID and OAuth secret. Then click Authorize GitLab and approve as above.
The GitLab host must be a real, reachable HTTPS address. Pangea rejects private, loopback and cloud-metadata addresses.
In the Pangea app
Browse the connected projects, merge requests and pipelines 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 deploy pipeline pass, and what went out in it?" It reads the pipeline and the commits behind it.
- "Production broke after the last merge. What changed?" It matches the incident window with merged MRs and reads the diff.
- "File an issue for this and link the failing pipeline." Name the project and review the issue 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. GitLab 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
- On your own GitLab instance, you create the OAuth application once. After that, connecting works the same as on gitlab.com.
- To widen access later, connect again with more options turned on. Reconnecting the same account updates the existing connection instead of adding a new one.
- Tokens are stored encrypted and refreshed automatically.