{
  "@context": "https://schema.org",
  "@id": "https://aggr.aymericbeaumet.com/items/ampcode-com/2026-10-12-you-ve-got-comments/#webpage",
  "@type": [
    "WebPage",
    "ArchiveComponent"
  ],
  "articleBody": "Amp now follows up on GitHub pull requests it opens. Comments, reviews, and CI results show up in the same thread.\n\nWhen Amp opens a PR, the agent can now subscribe to the PR's comments, reviews, and CI for its latest commit. A failing check or a reviewer's question shows up in the same thread, and Amp already has the context to deal with it.\n\n![Amp opening a pull request, subscribing to its updates, then receiving the CI results and a review in the same thread](https://ampcode.com/news/github-listeners-pr-followup.avif)\n\nThis is enabled by our new first-class support for [GitHub Webhooks](https://ampcode.com/docs/github#github-webhooks). In contrast to our existing, more generic [webhook support](https://ampcode.com/docs/orbs/event-driven), the new GitHub Webhook integration centrally handles all requests on the Amp side and then lets you (and your agent) decide whether to forward them to a single orb or to a new one each time. An agent can subscribe to certain events or can set up a subscription that spawns new orbs.\n\n## A New Orb for Every New GitHub Issue or PR\n\nAsk Amp to start a new orb for every new issue or PR in a repository. You can also limit it to ones opened with a certain label. You don't need to keep the thread where you set it up.\n\n![A request to start a new orb for every new issue in acme/website, the subscription tool call, and Amp noting that the thread can be archived](https://ampcode.com/news/github-listeners-spawner.avif)\n\nEach new issue or PR gets its own orb, which reads it and has a summary waiting when you open the thread. Later comments on that issue or PR go to the same thread, so the conversation stays in one place.\n\n![A new Amp thread started for a newly opened pull request, summarizing what the pull request changes](https://ampcode.com/news/github-listeners-new-pr-v2.avif)\n\nYou manage these in **Settings → Integrations & MCP → GitHub**, where you can edit or pause them and see the orbs each one started.\n\n![The GitHub Event Subscriptions table in Settings with two orb spawners and a pull request subscription](https://ampcode.com/news/github-listeners-settings-v3.avif)\n\nRead the [docs](https://ampcode.com/docs/github#github-listeners) to find out how to watch CI when you push to `main`, follow an existing issue or PR, and ask Puck what Amp is following.\n\n[Install the Amp GitHub App](https://ampcode.com/docs/github#connect-github) on your repository to get started.\n",
  "authors": [],
  "captured_at": "2026-10-12T22:35:36.108955126+00:00",
  "category": "programming",
  "content_html": "<p>Amp now follows up on GitHub pull requests it opens. Comments, reviews, and CI results show up in the same thread.</p>\n<p>When Amp opens a PR, the agent can now subscribe to the PR's comments, reviews, and CI for its latest commit. A failing check or a reviewer's question shows up in the same thread, and Amp already has the context to deal with it.</p>\n<p><picture class=\"article-picture article-picture-fallback\" style=\"--image-ratio:16 / 9\"><img src=\"https://ampcode.com/news/github-listeners-pr-followup.avif\" alt=\"Amp opening a pull request, subscribing to its updates, then receiving the CI results and a review in the same thread\" loading=\"eager\" decoding=\"async\" fetchpriority=\"high\" referrerpolicy=\"no-referrer\" class=\"progressive-image\"></picture></p>\n<p>This is enabled by our new first-class support for <a target=\"_blank\" rel=\"noopener noreferrer\" href=\"https://ampcode.com/docs/github#github-webhooks\">GitHub Webhooks</a>. In contrast to our existing, more generic <a target=\"_blank\" rel=\"noopener noreferrer\" href=\"https://ampcode.com/docs/orbs/event-driven\">webhook support</a>, the new GitHub Webhook integration centrally handles all requests on the Amp side and then lets you (and your agent) decide whether to forward them to a single orb or to a new one each time. An agent can subscribe to certain events or can set up a subscription that spawns new orbs.</p>\n<h2>A New Orb for Every New GitHub Issue or PR</h2>\n<p>Ask Amp to start a new orb for every new issue or PR in a repository. You can also limit it to ones opened with a certain label. You don't need to keep the thread where you set it up.</p>\n<p><picture class=\"article-picture article-picture-fallback\" style=\"--image-ratio:16 / 9\"><img src=\"https://ampcode.com/news/github-listeners-spawner.avif\" alt=\"A request to start a new orb for every new issue in acme/website, the subscription tool call, and Amp noting that the thread can be archived\" loading=\"lazy\" decoding=\"async\" fetchpriority=\"low\" referrerpolicy=\"no-referrer\" class=\"progressive-image\"></picture></p>\n<p>Each new issue or PR gets its own orb, which reads it and has a summary waiting when you open the thread. Later comments on that issue or PR go to the same thread, so the conversation stays in one place.</p>\n<p><picture class=\"article-picture article-picture-fallback\" style=\"--image-ratio:16 / 9\"><img src=\"https://ampcode.com/news/github-listeners-new-pr-v2.avif\" alt=\"A new Amp thread started for a newly opened pull request, summarizing what the pull request changes\" loading=\"lazy\" decoding=\"async\" fetchpriority=\"low\" referrerpolicy=\"no-referrer\" class=\"progressive-image\"></picture></p>\n<p>You manage these in <strong>Settings → Integrations &amp; MCP → GitHub</strong>, where you can edit or pause them and see the orbs each one started.</p>\n<p><picture class=\"article-picture article-picture-fallback\" style=\"--image-ratio:16 / 9\"><img src=\"https://ampcode.com/news/github-listeners-settings-v3.avif\" alt=\"The GitHub Event Subscriptions table in Settings with two orb spawners and a pull request subscription\" loading=\"lazy\" decoding=\"async\" fetchpriority=\"low\" referrerpolicy=\"no-referrer\" class=\"progressive-image\"></picture></p>\n<p>Read the <a target=\"_blank\" rel=\"noopener noreferrer\" href=\"https://ampcode.com/docs/github#github-listeners\">docs</a> to find out how to watch CI when you push to <code>main</code>, follow an existing issue or PR, and ask Puck what Amp is following.</p>\n<p><a target=\"_blank\" rel=\"noopener noreferrer\" href=\"https://ampcode.com/docs/github#connect-github\">Install the Amp GitHub App</a> on your repository to get started.</p>\n",
  "content_markdown": "Amp now follows up on GitHub pull requests it opens. Comments, reviews, and CI results show up in the same thread.\n\nWhen Amp opens a PR, the agent can now subscribe to the PR's comments, reviews, and CI for its latest commit. A failing check or a reviewer's question shows up in the same thread, and Amp already has the context to deal with it.\n\n![Amp opening a pull request, subscribing to its updates, then receiving the CI results and a review in the same thread](https://ampcode.com/news/github-listeners-pr-followup.avif)\n\nThis is enabled by our new first-class support for [GitHub Webhooks](https://ampcode.com/docs/github#github-webhooks). In contrast to our existing, more generic [webhook support](https://ampcode.com/docs/orbs/event-driven), the new GitHub Webhook integration centrally handles all requests on the Amp side and then lets you (and your agent) decide whether to forward them to a single orb or to a new one each time. An agent can subscribe to certain events or can set up a subscription that spawns new orbs.\n\n## A New Orb for Every New GitHub Issue or PR\n\nAsk Amp to start a new orb for every new issue or PR in a repository. You can also limit it to ones opened with a certain label. You don't need to keep the thread where you set it up.\n\n![A request to start a new orb for every new issue in acme/website, the subscription tool call, and Amp noting that the thread can be archived](https://ampcode.com/news/github-listeners-spawner.avif)\n\nEach new issue or PR gets its own orb, which reads it and has a summary waiting when you open the thread. Later comments on that issue or PR go to the same thread, so the conversation stays in one place.\n\n![A new Amp thread started for a newly opened pull request, summarizing what the pull request changes](https://ampcode.com/news/github-listeners-new-pr-v2.avif)\n\nYou manage these in **Settings → Integrations & MCP → GitHub**, where you can edit or pause them and see the orbs each one started.\n\n![The GitHub Event Subscriptions table in Settings with two orb spawners and a pull request subscription](https://ampcode.com/news/github-listeners-settings-v3.avif)\n\nRead the [docs](https://ampcode.com/docs/github#github-listeners) to find out how to watch CI when you push to `main`, follow an existing issue or PR, and ask Puck what Amp is following.\n\n[Install the Amp GitHub App](https://ampcode.com/docs/github#connect-github) on your repository to get started.\n",
  "dateCreated": "2026-10-12T22:35:36.108955126+00:00",
  "date_created": "2026-10-12T00:00:00+00:00",
  "date_modified": "2026-10-12T00:00:00+00:00",
  "date_published": "2026-10-12T00:00:00+00:00",
  "description": "Amp now follows up on GitHub pull requests it opens. Comments, reviews, and CI results show up in the same thread. When Amp opens a PR, the agent can now subscribe to the PR's comments, reviews, and CI for its latest commit. A failing…",
  "external_url": "https://ampcode.com/news/github-listeners",
  "git": {
    "commit": "ebb0941c5c06a2ab2377342d607535262a3e969e",
    "path": "items/ampcode-com/2026/10/2026-10-12-you-ve-got-comments.md",
    "permalink": "https://github.com/aymericbeaumet/aggr-instance/blob/ebb0941c5c06a2ab2377342d607535262a3e969e/items/ampcode-com/2026/10/2026-10-12-you-ve-got-comments.md"
  },
  "id": "urn:aggr:item:a0f21978c85977e8afc69f451767da7e0cc7101b",
  "isBasedOn": {
    "@id": "https://ampcode.com/news/github-listeners"
  },
  "mainEntity": {
    "@id": "https://ampcode.com/news/github-listeners",
    "@type": "CreativeWork",
    "archivedAt": {
      "@id": "https://aggr.aymericbeaumet.com/items/ampcode-com/2026-10-12-you-ve-got-comments/#webpage"
    },
    "dateModified": "2026-10-12T00:00:00+00:00",
    "datePublished": "2026-10-12T00:00:00+00:00",
    "headline": "You've Got Comments",
    "image": {
      "@type": "ImageObject",
      "caption": "Amp opening a pull request, subscribing to its updates, then receiving the CI results and a review in the same thread",
      "height": 90,
      "url": "https://ampcode.com/news/github-listeners-pr-followup.avif",
      "width": 160
    },
    "timeRequired": "PT2M",
    "url": "https://ampcode.com/news/github-listeners",
    "wordCount": 291
  },
  "name": "Archived snapshot: You've Got Comments",
  "preview": {
    "alt": "Amp opening a pull request, subscribing to its updates, then receiving the CI results and a review in the same thread",
    "color": null,
    "height": 90,
    "placeholder": {
      "data_url": "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAQAAAC1HAwCAAAAC0lEQVR42mNk+A8AAQUBAScY42YAAAAASUVORK5CYII=",
      "hash": ""
    },
    "url": "https://ampcode.com/news/github-listeners-pr-followup.avif",
    "width": 160
  },
  "reading_minutes": 2,
  "replicated_at": null,
  "source": "ampcode-com",
  "source_name": "Amp News",
  "summary": "Amp now follows up on GitHub pull requests it opens. Comments, reviews, and CI results show up in the same thread. When Amp opens a PR, the agent can now subscribe to the PR's comments, reviews, and CI for its latest commit. A failing check or a reviewer's question shows up in the same thread, and Amp already has the context to deal with it. This is enabled by our new first-class support for GitHub Webhooks. In contrast to our existing, more generic webhook support, the new GitHub Webhook integration centrally handles all requests on the Amp side and then lets you (and your agent) decide whether to forward them to a single orb or to a new one each time. An agent can subscribe to certain events or can set up a subscription that spawns new orbs. A New Orb for Every New GitHub Issue or PR Ask Amp to start a new orb for every new issue or PR in a repository. You can also limit it to ones opened with a certain label. You don't need to keep the thread where you set it up. Each new issue or PR gets its own orb, which reads it and has a summary waiting when you open the thread. Later comments on that issue or PR go to the same thread, so the conversation stays in one place. You manage these in Settings → MCP & Integrations → GitHub, where you can edit or pause them and see the orbs each one started. Read the docs to find out how to watch CI when you push to main, follow an existing issue or PR, and ask Puck what Amp is following. Install the Amp GitHub App on your repository to get started.",
  "tags": [],
  "temporalCoverage": "2026-10-12T22:35:36.108955126+00:00",
  "title": "You've Got Comments",
  "url": "https://aggr.aymericbeaumet.com/items/ampcode-com/2026-10-12-you-ve-got-comments/",
  "word_count": 291
}