# Amp — GitLab Integration

- Company: Amp (ampcode.com)
- Announced: 2026-11-05
- Category: capability-change
- Coverage: not counted
- Announcement: yes
- Group: announcements
- Source: https://ampcode.com/news/gitlab
- Record: https://forck.live/items/32262-gitlab-integration
- Subject: Amp

Amp now integrates with GitLab, on gitlab.com and on self-managed instances, letting users start projects from their GitLab repositories. Orbs clone and push as the user and come with glab signed in, so the agent can open merge requests, comment on them, and read issues and pipelines. Amp can also subscribe to comments and CI for a merge request it opens, so a reviewer's request or a failed pipeline lands in the thread that wrote the code and Amp already has the context. Users can ask Amp to start a new orb for every new merge request or issue in a project, and each one reads it and has a summary ready when the thread is opened, with later comments going to that same thread. Workspace admins can run a spawner as a service account, and all of these are managed in Settings → Integrations & MCP → GitLab under Event Subscriptions, where they can be paused or deleted. Each person connects GitLab in Settings → Integrations & MCP, then a group Owner installs Push Updates once for the workspace.

## Evidence

Verbatim from https://ampcode.com/news/gitlab:

> Amp now integrates with GitLab, on gitlab.com and on self-managed instances.
> 
> Connect your GitLab account and you can start projects from your GitLab repositories. Orbs clone and push as you and come with glab signed in, so the agent can open merge requests, comment on them, and read issues and pipelines.
> 
> Amp can also subscribe to comments and CI for a merge request it opens. A reviewer's request or a failed pipeline lands in the thread that wrote the code, so Amp already has the context.
> 
> A New Orb for Every New Merge Request or Issue
> 
> Ask Amp to start a new orb for every new merge request or issue in a project. You don't need to keep the thread where you set it up. See Create an Orb Spawner .
> 
> Each new merge request or issue gets its own orb, which reads it and has a summary ready when you open the thread. Later comments go to that same thread. Workspace admins can also run a spawner as a service account .
> 
> You manage all of these in Settings → Integrations & MCP → GitLab under Event Subscriptions , where you can pause or delete them, edit a spawner, and see the orbs each spawner started.
> 
> Set It Up
> 
> Each person connects GitLab in Settings → Integrations & MCP .

---

Record: https://forck.live/items/32262-gitlab-integration
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md