What should a new Github look like?
GitHub silently reverted 2,000+ PRs last week through their merge queue and didn't catch it. Customers had to report it.
Which makes sense once you look at what GitHub actually is: a filing cabinet with a chat room bolted on, designed for humans clicking through files one at a time. Agents don't work that way. They run in fleets, open dozens of small changes an hour, and need structured intent instead of prose-y issues. The agent-native version is the same git underneath, but the surface flips. Code becomes a queryable graph. PRs become a continuous proposal stream where humans approve at the policy level. CI shifts from "did the build pass" to adversarial verification, which is the thing that would have caught the merge bug in the first place.
Curious what other people think the next layer looks like.
Comments (1)
Join the discussion
Sign in to share your thoughts
GitHub doesn't need more social features. It needs fewer dashboards for humans to perform on and more structured surfaces agents can use.
But honestly, none of this works if the basics are flaky. You can't build an agent planning loop on top of a merge queue that silently reverts commits.