{
  "@context": "https://schema.org",
  "@id": "https://aggr.aymericbeaumet.com/items/ampcode-com/2026-11-05-gitlab-integration/#webpage",
  "@type": [
    "WebPage",
    "ArchiveComponent"
  ],
  "articleBody": "Amp now integrates with GitLab, on gitlab.com and on self-managed instances.\n\nConnect 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.\n\nAmp 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.\n\n![An Amp thread receiving a comment on merge request !1 in amp-test/api, wrapping the README at 100 columns as the reviewer asked, then receiving the CI result: all pipelines complete](https://static.ampcode.com/news/gitlab-mr-followup.avif) ![An Amp thread receiving a comment on merge request !1 in amp-test/api, wrapping the README at 100 columns as the reviewer asked, then receiving the CI result: all pipelines complete](https://static.ampcode.com/news/gitlab-mr-followup-dark.avif)\n\n## A New Orb for Every New Merge Request or Issue\n\nAsk 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](https://ampcode.com/docs/gitlab#create-an-orb-spawner).\n\nEach 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](https://ampcode.com/docs/gitlab#run-a-spawner-as-a-service-account).\n\nYou 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.\n\n![The GitLab Event Subscriptions table in Settings with a spawner for new amp-test/api issues expanded to show its Spawned Orbs, above subscriptions to issue #5, issue #1, and merge request !1](https://static.ampcode.com/news/gitlab-event-subscriptions.avif) ![The GitLab Event Subscriptions table in Settings with a spawner for new amp-test/api issues expanded to show its Spawned Orbs, above subscriptions to issue #5, issue #1, and merge request !1](https://static.ampcode.com/news/gitlab-event-subscriptions-dark.avif)\n\n## Set It Up\n\nEach person connects GitLab in [Settings → Integrations & MCP](https://ampcode.com/settings/integrations#gitlab). Then a group Owner installs Push Updates once for the workspace, with one button in [Workspace Settings → Integrations & MCP](https://ampcode.com/workspace/integrations).\n\nAmp also supports self-managed GitLab. See [Self-Managed Instances](https://ampcode.com/docs/gitlab#self-managed-instances).\n\n[Connect GitLab](https://ampcode.com/docs/gitlab#connect-gitlab) to get started.\n",
  "authors": [],
  "captured_at": "2026-11-05T23:32:43.152740887+00:00",
  "category": "programming",
  "content_html": "<p>Amp now integrates with GitLab, on gitlab.com and on self-managed instances.</p>\n<p>Connect your GitLab account and you can start projects from your GitLab repositories. Orbs clone and push as you and come with <code>glab</code> signed in, so the agent can open merge requests, comment on them, and read issues and pipelines.</p>\n<p>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.</p>\n<p><picture class=\"article-picture article-picture-fallback\" style=\"--image-ratio:16 / 9\"><img src=\"https://static.ampcode.com/news/gitlab-mr-followup.avif\" alt=\"An Amp thread receiving a comment on merge request !1 in amp-test/api, wrapping the README at 100 columns as the reviewer asked, then receiving the CI result: all pipelines complete\" loading=\"eager\" decoding=\"async\" fetchpriority=\"high\" referrerpolicy=\"no-referrer\" class=\"progressive-image\"></picture> <picture class=\"article-picture article-picture-fallback\" style=\"--image-ratio:16 / 9\"><img src=\"https://static.ampcode.com/news/gitlab-mr-followup-dark.avif\" alt=\"An Amp thread receiving a comment on merge request !1 in amp-test/api, wrapping the README at 100 columns as the reviewer asked, then receiving the CI result: all pipelines complete\" loading=\"lazy\" decoding=\"async\" fetchpriority=\"low\" referrerpolicy=\"no-referrer\" class=\"progressive-image\"></picture></p>\n<h2>A New Orb for Every New Merge Request or Issue</h2>\n<p>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 <a target=\"_blank\" rel=\"noopener noreferrer\" href=\"https://ampcode.com/docs/gitlab#create-an-orb-spawner\">Create an Orb Spawner</a>.</p>\n<p>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 <a target=\"_blank\" rel=\"noopener noreferrer\" href=\"https://ampcode.com/docs/gitlab#run-a-spawner-as-a-service-account\">service account</a>.</p>\n<p>You manage all of these in <strong>Settings → Integrations &amp; MCP → GitLab</strong> under <strong>Event Subscriptions</strong>, where you can pause or delete them, edit a spawner, and see the orbs each spawner started.</p>\n<p><picture class=\"article-picture article-picture-fallback\" style=\"--image-ratio:16 / 9\"><img src=\"https://static.ampcode.com/news/gitlab-event-subscriptions.avif\" alt=\"The GitLab Event Subscriptions table in Settings with a spawner for new amp-test/api issues expanded to show its Spawned Orbs, above subscriptions to issue #5, issue #1, and merge request !1\" loading=\"lazy\" decoding=\"async\" fetchpriority=\"low\" referrerpolicy=\"no-referrer\" class=\"progressive-image\"></picture> <picture class=\"article-picture article-picture-fallback\" style=\"--image-ratio:16 / 9\"><img src=\"https://static.ampcode.com/news/gitlab-event-subscriptions-dark.avif\" alt=\"The GitLab Event Subscriptions table in Settings with a spawner for new amp-test/api issues expanded to show its Spawned Orbs, above subscriptions to issue #5, issue #1, and merge request !1\" loading=\"lazy\" decoding=\"async\" fetchpriority=\"low\" referrerpolicy=\"no-referrer\" class=\"progressive-image\"></picture></p>\n<h2>Set It Up</h2>\n<p>Each person connects GitLab in <a target=\"_blank\" rel=\"noopener noreferrer\" href=\"https://ampcode.com/settings/integrations#gitlab\">Settings → Integrations &amp; MCP</a>. Then a group Owner installs Push Updates once for the workspace, with one button in <a target=\"_blank\" rel=\"noopener noreferrer\" href=\"https://ampcode.com/workspace/integrations\">Workspace Settings → Integrations &amp; MCP</a>.</p>\n<p>Amp also supports self-managed GitLab. See <a target=\"_blank\" rel=\"noopener noreferrer\" href=\"https://ampcode.com/docs/gitlab#self-managed-instances\">Self-Managed Instances</a>.</p>\n<p><a target=\"_blank\" rel=\"noopener noreferrer\" href=\"https://ampcode.com/docs/gitlab#connect-gitlab\">Connect GitLab</a> to get started.</p>\n",
  "content_markdown": "Amp now integrates with GitLab, on gitlab.com and on self-managed instances.\n\nConnect 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.\n\nAmp 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.\n\n![An Amp thread receiving a comment on merge request !1 in amp-test/api, wrapping the README at 100 columns as the reviewer asked, then receiving the CI result: all pipelines complete](https://static.ampcode.com/news/gitlab-mr-followup.avif) ![An Amp thread receiving a comment on merge request !1 in amp-test/api, wrapping the README at 100 columns as the reviewer asked, then receiving the CI result: all pipelines complete](https://static.ampcode.com/news/gitlab-mr-followup-dark.avif)\n\n## A New Orb for Every New Merge Request or Issue\n\nAsk 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](https://ampcode.com/docs/gitlab#create-an-orb-spawner).\n\nEach 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](https://ampcode.com/docs/gitlab#run-a-spawner-as-a-service-account).\n\nYou 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.\n\n![The GitLab Event Subscriptions table in Settings with a spawner for new amp-test/api issues expanded to show its Spawned Orbs, above subscriptions to issue #5, issue #1, and merge request !1](https://static.ampcode.com/news/gitlab-event-subscriptions.avif) ![The GitLab Event Subscriptions table in Settings with a spawner for new amp-test/api issues expanded to show its Spawned Orbs, above subscriptions to issue #5, issue #1, and merge request !1](https://static.ampcode.com/news/gitlab-event-subscriptions-dark.avif)\n\n## Set It Up\n\nEach person connects GitLab in [Settings → Integrations & MCP](https://ampcode.com/settings/integrations#gitlab). Then a group Owner installs Push Updates once for the workspace, with one button in [Workspace Settings → Integrations & MCP](https://ampcode.com/workspace/integrations).\n\nAmp also supports self-managed GitLab. See [Self-Managed Instances](https://ampcode.com/docs/gitlab#self-managed-instances).\n\n[Connect GitLab](https://ampcode.com/docs/gitlab#connect-gitlab) to get started.\n",
  "dateCreated": "2026-11-05T23:32:43.152740887+00:00",
  "date_created": "2026-11-05T00:00:00+00:00",
  "date_modified": "2026-11-05T00:00:00+00:00",
  "date_published": "2026-11-05T00:00:00+00:00",
  "description": "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…",
  "external_url": "https://ampcode.com/news/gitlab",
  "git": {
    "commit": "20068632b65d2830a2d54f25ca1d90d697bea2c0",
    "path": "items/ampcode-com/2026/11/2026-11-05-gitlab-integration.md",
    "permalink": "https://github.com/aymericbeaumet/aggr-instance/blob/20068632b65d2830a2d54f25ca1d90d697bea2c0/items/ampcode-com/2026/11/2026-11-05-gitlab-integration.md"
  },
  "id": "urn:aggr:item:d707928a1a66c74a30485f5c95a040316a9ef4ae",
  "isBasedOn": {
    "@id": "https://ampcode.com/news/gitlab"
  },
  "mainEntity": {
    "@id": "https://ampcode.com/news/gitlab",
    "@type": "CreativeWork",
    "archivedAt": {
      "@id": "https://aggr.aymericbeaumet.com/items/ampcode-com/2026-11-05-gitlab-integration/#webpage"
    },
    "dateModified": "2026-11-05T00:00:00+00:00",
    "datePublished": "2026-11-05T00:00:00+00:00",
    "headline": "GitLab Integration",
    "image": {
      "@type": "ImageObject",
      "caption": null,
      "height": 90,
      "url": "https://ampcode.com/og?_template=news&_version=7&title=GitLab+Integration&date=November+5%2C+2026&tagline=Connect+gitlab.com+or+your+own+GitLab+instance+to+Amp.&screenshot=https%3A%2F%2Fstatic.ampcode.com%2Fnews%2Fgitlab-mr-followup.avif&sig=879c88409ea968062fa54a6c63eeacf216a1c3fe38c3ecbaa90c9c79b5075264",
      "width": 160
    },
    "timeRequired": "PT2M",
    "url": "https://ampcode.com/news/gitlab",
    "wordCount": 247
  },
  "name": "Archived snapshot: GitLab Integration",
  "preview": {
    "alt": null,
    "color": null,
    "height": 90,
    "placeholder": {
      "data_url": "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAQAAAC1HAwCAAAAC0lEQVR42mNk+A8AAQUBAScY42YAAAAASUVORK5CYII=",
      "hash": ""
    },
    "url": "https://ampcode.com/og?_template=news&_version=7&title=GitLab+Integration&date=November+5%2C+2026&tagline=Connect+gitlab.com+or+your+own+GitLab+instance+to+Amp.&screenshot=https%3A%2F%2Fstatic.ampcode.com%2Fnews%2Fgitlab-mr-followup.avif&sig=879c88409ea968062fa54a6c63eeacf216a1c3fe38c3ecbaa90c9c79b5075264",
    "width": 160
  },
  "reading_minutes": 2,
  "replicated_at": null,
  "source": "ampcode-com",
  "source_name": "Amp News",
  "summary": "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. Then a group Owner installs Push Updates once for the workspace, with one button in Workspace Settings → Integrations & MCP. Amp also supports self-managed GitLab. See Self-Managed Instances. Connect GitLab to get started.",
  "tags": [],
  "temporalCoverage": "2026-11-05T23:32:43.152740887+00:00",
  "title": "GitLab Integration",
  "url": "https://aggr.aymericbeaumet.com/items/ampcode-com/2026-11-05-gitlab-integration/",
  "word_count": 247
}