Amp adds GitLab integration with orbs and merge request spawners
Amp added a GitLab integration for gitlab.com and self-managed servers. Orbs work with your GitLab identity and an authenticated glab, so the agent can open merge requests, read issues and pipelines, and follow up on review comments and CI failures; orb spawners can even open a thread per new merge request or issue.
Key points
- GitLab support covers both gitlab.com and self-managed instances.
- Orbs clone and push with the connected user's identity and ship with glab signed in, enabling merge requests, comments, issues and pipeline reads.
- Amp can subscribe to review comments and CI results for a merge request it opened, so feedback returns to the thread that wrote the code.
- Orb spawners create a separate orb per new merge request or issue, each with a summary ready when you open the thread.
- Setup takes two steps: each person connects GitLab in Settings → Integrations & MCP, and a group Owner installs Push Updates once for the workspace.
Amp has added GitLab as a supported host, covering gitlab.com and self-managed installations. Once an account is linked, a developer starts projects from GitLab repositories; the resulting orb checks out and pushes code under that person's identity and arrives with glab already authenticated, so the agent can open merge requests, reply on them, and read issues and pipelines.
A second piece is the orb spawner: point one at a project and every new merge request or issue gets its own orb, which reads the item and has a summary ready when you open it, with later comments landing in the same thread. Review-comment and CI subscriptions sit in Settings → Integrations & MCP; a group Owner installs Push Updates once per workspace.
Real-world use
- A team running GitLab on self-managed infrastructure that wants an agent to triage new issues and draft merge requests without leaving their own server.
- A project with heavy review traffic where each new merge request gets an orb that summarises the change and picks up reviewer comments in the same thread.
- A release pipeline that fails often, with CI results routed back to the orb that authored the change so the agent can fix it with full context.
- An on-call rotation where an admin-run service account spawner keeps producing first-pass summaries of incoming merge requests overnight.
Why it matters
GitLab teams no longer have to move work to GitHub to get an agent in the loop: reviews, comments and CI results come back to the thread that produced the code, which is where the context already lives.