Thursday, 19 November 2026, story 7 of 7
GitHub CLI 2.105.0 lets agents wait on pull request events
The new gh event listen command replaces polling loops, but it is in preview and needs access to Event Streams, which has a waitlist.

What happened
GitHub has added event streaming to its command-line tool. According to the GitHub Changelog, gh v2.105.0 includes gh event listen, which takes a pull request URL and the events to watch, such as a submitted review. It opens a stream and prints each event as a line of JSON.
By default it exits after the first event. Flags set a count (--count), keep it listening (--follow), or stop it (--timeout). It can wait on reviews, state and head changes, merge conflicts and completed check suites. The commands are in preview and may change. They require Event Streams, in preview on GitHub.com, which has a waitlist.
What it means
Agents that merge or review code today often check a pull request in a loop. A single blocking command that exits on the first event is easier to write into a script, and it may spare agents from running repeated status calls. GitHub says gh pr create, gh pr view, gh run view, gh run watch and gh api now suggest gh event listen, so agents may switch to it without being told.
The limits matter. Access depends on the Event Streams waitlist, and the source gives no timing or pricing. Because the commands may change, anything built on them now risks rework. Teams with agent-driven review pipelines should look at the output format and flags, but keep a polling fallback until access is general.
What to do: Upgrade to gh v2.105.0, join the Event Streams waitlist if you run agent review loops, and keep polling as a fallback while the commands are in preview.
Source
- Wait for pull request events with GitHub CLI, GitHub Changelog
Filed under Coding tools. Published .
"What it means" is analysis, not reporting. Found an error? Write to daily@vibitely.com.