GitHub is now a real-time coordination layer between developers, agents, and automation.

With Event Streams, your agent sleeps while there’s no work and wakes as soon as there is. You get a faster loop between feedback and action, fewer wasted tokens and less rate-limit burn, and no polling loop to build or tune.

Without a webhook receiver, the usual way to keep up is polling: asking GitHub “did anything change?” over and over. That leaves you with a decision:

  • Poll often and you burn rate-limit budget on requests that mostly return nothing new.
  • Poll less often and review feedback sits until your next check.

How to receive pull request updates without polling

  1. Subscribe to a pull request.
  2. Connect to GitHub and keep the connection open to receive events.
  3. Receive an event when:
  • A review is submitted.
  • New commits are pushed.
  • A merge conflict appears.
  • The pull request is merged or closed.
  • There’s been a change to your pull request’s check suites.
  • A check suite status changes (one event per check suite).

No public webhook endpoint is required, so your agent can receive events while running on your laptop.

To get access, sign up for the Event Streams waitlist.

To learn more, see the Event Streams documentation.

Availability

Event Streams is available in preview on all GitHub plans once approved on the waitlist.

Share your feedback in the GitHub Community discussion.