SATURDAY, NOVEMBER 21, 2026 Tech news, minus the noise.
N News Cast
LATEST
Home  /  Dev
Dev

GitHub CLI 2.105 Lets You Wait for Pull Request Events Instead of Polling in a Loop

GitHub CLI 2.105.0 adds GitHub Event Streams support, letting you wait for a pull request event with a single command instead of polling in a loop.

GitHub CLI 2.105 Lets You Wait for Pull Request Events Instead of Polling in a Loop
Source: Markus Spiske (CC0), via Wikimedia Commons

GitHub CLI 2.105 Adds Event Streams

GitHub CLI 2.105.0 adds support for GitHub Event Streams, which means you can now wait for a pull request event with a single command instead of polling in a loop. If you have ever written a script that checks a pull request every ten seconds to see whether the checks passed, you know exactly how wasteful that pattern is. Now the CLI can wait for the event to arrive and then act on it.

The feature is aimed squarely at two audiences: developers writing automation, and the coding agents that now do a large share of that automation. An agent that polls a pull request in a loop burns API calls, burns tokens on repeated checks, and still finds out about changes late. An agent that waits for an event gets told the moment something changes, and spends the time in between doing nothing, which is exactly what waiting should cost.

GitHub has been building toward this for a while. Event Streams give clients a way to subscribe to repository activity instead of hammering the API, and putting that capability in the CLI makes it available to every script and agent that already uses gh commands. There is nothing to install beyond the update itself.

Why Polling Was the Problem

Polling is one of those habits that feels harmless until you measure it. A script that checks a pull request every 30 seconds makes 120 API calls an hour, and most of those calls return the same answer: nothing changed yet. Multiply that by every developer, every CI job, and every agent session in an organization, and you get a steady background load that exists only because nobody built a better way to wait.

The costs are not just API calls. Polling loops in CI pipelines keep runners busy doing nothing, and agents that poll burn context on repeated status checks that contain no new information. In a year when coding agents run thousands of sessions a day, the waste compounds. Event Streams fix the problem at the root: instead of asking again and again, you wait once and get notified.

The pattern is familiar from elsewhere in the stack. Webhooks have done this for servers for years, and message queues do it for services. What GitHub CLI 2.105 does is bring the same idea to the terminal, where developers and agents actually work. It is a small change with a large effect on how much busywork automation has to do.

A Week of Agent Tooling

GitHub CLI 2.105 does not arrive in a vacuum. The past week has been crowded with tools for the agent era: Cloudflare open-sourced Kitesurf, its browser engine for AI agents; AWS published its Emulator, a local cloud emulator written entirely by AI agents; and OpenAI shipped a security CLI that uses Codex to find and patch vulnerabilities. The common thread is that the industry is rebuilding its tooling around agents as first-class users, not as an afterthought.

Event Streams fit that trend. An agent that can wait for a pull request event is an agent that can run longer, cheaper, and with less noise. The same is true of the VS Code 1.147 update, which turned the editor into an agent control center, and the Python 3.15 release, which keeps the language agents run on current. Each piece on its own is minor. Together, they describe a toolchain being rebuilt for a different kind of user.

For human developers, the benefit is simpler: scripts that wait properly are scripts you do not have to babysit. A deployment script that waits for the checks to pass and then proceeds is a script you can trust, and a script you can trust is one you stop thinking about.

How to Use It

Update the CLI through your usual route: brew upgrade gh on macOS, your package manager on Linux, or winget on Windows. Once you are on 2.105.0, the Event Streams support is available for pull request workflows, and the GitHub docs cover the exact command shape for the events you want to watch.

Start with one script. Pick the polling loop you hate most, the one that checks a pull request or a workflow run every minute, and replace it with an event wait. You will know within a day whether the change was worth it, because the script will either do its job quietly or it will not. That is the whole test, and it is the same test every tool in this space has to pass: does it remove work, or does it just move the work somewhere else? GitHub CLI 2.105 removes work, and for a tool that lives in the terminal, that is the highest praise there is.

The Bottom Line on GitHub CLI 2.105

GitHub CLI 2.105 is not a headline release, and it does not need to be. Event Streams support removes a piece of busywork that every developer and every coding agent has tolerated for years, and it does so in the tool they already use. The Rust Anything project showed the same lesson this month: the tools that win are the ones that remove friction instead of adding features. Update gh, replace one polling loop, and enjoy the quiet.

AS
News Cast Editorial Team

We cover AI, gadgets, startups and security — original reporting and explainers, written by humans, for humans. Got a tip? Reach us via the contact page.