Sourcegraph's Amp Learns to Watch Its Own PRs: Comments, Reviews, and CI in a Single Thread

Amp, Sourcegraph's coding agent, no longer abandons a pull request as soon as it opens it. It now subscribes to comments, reviews, and CI results on the latest commit of its PR. If a check fails or a reviewer asks a question, the event arrives in the same thread where the agent wrote the code. The agent already has the task context, so there is nothing to explain. The update shipped on 12 October 2026 and relies on a new GitHub Webhooks integration.

How the subscription works

Previously, Amp had more general support for event webhooks for orbs (Amp's term for the agent's working environment). The new GitHub integration works differently: Amp itself receives all incoming requests centrally. From there, you or the agent decide where to forward them: to one specific orb, or to a new orb for each event.

The agent can subscribe to specific events, such as activity on its own PR. It can also create a subscription that spawns new orbs. You don't need to keep the thread where you set all this up: the subscription lives separately from it, and Amp states explicitly that the thread can be archived.

A new orb for every issue or PR

The second scenario is built for a stream of incoming tasks. You ask Amp to launch a separate orb for every new issue or PR in a repository. The announcement's example is every new issue in the acme/website repository. You can narrow the selection to items opened with a particular label.

Each such orb reads its own issue or PR, and by the time you open the thread, a short summary is already there. Subsequent comments go into the same thread, so the discussion doesn't get scattered across several sessions.

Key parameters of the update:

• three types of signals on a PR's latest commit: comments, reviews, CI;
• two routing modes: to one existing orb, or to a new orb for each event;
• label filtering for automatically launched orbs;
• subscription management in Settings → MCP & Integrations → GitHub: editing, pausing, and a list of launched orbs for each subscription;
• the screenshot of the GitHub Event Subscriptions table shows two orb spawners and one PR subscription.

What to do with it

Start by installing the Amp GitHub App on the repository you need. After that, it is enough to ask the agent in a regular thread to subscribe to the PR it opened, or to launch orbs for new issues. The subscriptions table in settings is a convenient way to check what is actually running and to pause anything unnecessary.

The documentation describes other scenarios as well. You can watch CI after a push to main, subscribe to an existing issue or PR, or ask Puck what Amp is currently tracking.

In practice, the benefit is a shorter loop of "PR opened, CI failed, a human noticed, went back to the agent." The agent reacts to red CI and review comments in the same context in which it wrote the code. Some caution is warranted with the auto-spawner: on an active repository it creates an orb for every issue or PR, so it is worth setting a label filter right away. The announcement does not disclose limits on the number of orbs or pricing terms, so check the Amp documentation for those.