GitHub Event Streams lets agents skip polling for pull requests
A new preview feature pushes pull request events straight to a long-lived connection, so a coding agent on your laptop no longer needs its own webhook endpoint.
GitHub has put Event Streams into preview, a way for agents and automation to get pull request updates without polling the API. An agent opens a connection to GitHub and keeps it open, and GitHub pushes an event the moment something happens: a review submitted, new commits pushed, a merge conflict appearing, a check suite status changing, or the pull request closing or merging.
The detail that matters is in the fine print: no public webhook endpoint is required. Webhooks have always needed a reachable URL to deliver to, which ruled out an agent running on your own machine. Event Streams works the other way round, so a local coding agent can hold the connection open itself. Access is behind a waitlist for now; once approved, it is available on every GitHub plan.
Why it matters: polling a pull request’s status is the default pattern in most coding-agent setups today, and it is a bad trade either way: poll often and you burn rate limit and tokens checking for nothing, poll rarely and the agent reacts late. Event Streams removes that trade-off for anyone building a review bot, a merge assistant, or a local agent that needs to act on PR activity as it happens.