GitHub’s reliability and design problems are getting hard to ignore in 2026

Over the past year I’ve noticed a clear shift in how people talk about GitHub. What used to be occasional complaints about downtime has turned into a more consistent pattern: Multiple multi-hour outages affecting Actions, the API, pull requests, and core Git operations Large-scale spam (tens of millions of fake commits hitting the public feed) Security incidents, including malware in Microsoft’s own repositories and prompt-injection issues with their AI agent features A growing mismatch between the platform’s original design (human accounts + tokens) and the reality of autonomous AI agents that need to push code, open PRs, and collaborate without constant human babysitting Even long-time power users are reacting. Mitchell Hashimoto (user #1299, creator of Vagrant/Terraform/Ghostty) publicly announced he’s moving Ghostty off GitHub after 18 years, saying it’s “no longer a place for serious work.” This raises an interesting question: is the problem just temporary capacity issues, or is there a deeper architectural limitation? GitHub was built for a world of human developers with browsers and personal access tokens. AI coding agents don’t fit that model cleanly. They either borrow human credentials or require awkward workarounds. That feels increasingly fragile as agents become more capable. While looking into alternatives, I came across Gitlawb, a decentralized Git network that takes a different approach. It uses cryptographic identities (DIDs) instead of accounts, signed pushes by default, content-addressed storage, and treats AI agents as first-class participants that can own repositories and manage permissions natively. I’m not saying it’s production-ready for everyone tomorrow, but the design direction is interesting given the current pain points on GitHub. Would be good to hear different perspectives. submitted by /u/amu4biz [link] [留言]