Mitchell Hashimoto, creator of the Ghostty terminal emulator and co-founder of HashiCorp, said Tuesday that the project will move off GitHub after a month of near-daily outages. The decision was announced in a blog post dated April 28, hours after GitHub's Elasticsearch cluster collapsed under what the company described as a likely botnet attack.
An 18-year breakup
Hashimoto's post is, by his own admission, a love letter that ends in goodbye. He's GitHub user 1299, joined in February 2008, and says he's opened the site every single day since. "I love GitHub more than a person should love a thing, and I'm mad at it," he wrote. The kind of line that gets quoted because it's true and slightly embarrassing.
The trigger was banal. For the past month, he kept a journal marking an X on every day a GitHub outage blocked his work. Almost every day got an X. The day he wrote the post, GitHub Actions was down for roughly two hours and he couldn't review pull requests. That's it. That's the reason.
Only Ghostty is moving. His personal projects stay on GitHub for now, and the existing repository will become a read-only mirror. Hashimoto hasn't picked a new home yet, saying only that talks are ongoing with "multiple providers (both commercial and FOSS)." Codeberg, GitLab, and self-hosted Forgejo are the obvious candidates, though he names none of them.
The timing is awkward
Hashimoto says he wrote the post a week before publishing, and that the timing of the April 27 Elasticsearch incident was coincidence. Sure. The footnote where he clarifies this is itself a small comedy: the Actions outage that prompted him to finalize the post was a different outage from the much larger one that hit the day before publication. Two unrelated GitHub failures bracketing one farewell.
The April 27 incident took down search-backed UI across GitHub for hours. Pull request lists rendered empty, issues vanished from views, projects failed to load. Git itself was fine. The platform on top of Git was not.
GitHub CTO Vlad Fedorov posted his own apology on the company blog the same day. He framed the reliability problems as a capacity story: agentic AI workflows have been hammering the platform since late 2025, and what was planned in October 2025 as a 10x capacity rebuild was rescoped in February to a 30x redesign. Whether that's a confession of bad planning or an honest read of a fast-moving industry depends on how charitable you feel.
And he's not alone
Hashimoto isn't moving alone. The same day his post went up, BookStack maintainer Dan Brown announced his project had finished migrating from GitHub to Codeberg. Brown's migration post is more procedural than dramatic, but it lands in the same week, and the framing overlaps: Microsoft-owned GitHub increasingly feels misaligned with open source values, and the AI tooling push is part of why.
BookStack started the move in mid-2024 with secondary repos. The main project sat on GitHub until Brown finally pushed it through at 3 AM on a Sunday after weeks of failed import attempts. The new Codeberg repo is now the source of truth; the old GitHub address will mirror it going forward.
One announcement is a personal note from a well-known maintainer. Two announcements in a single day, both citing reliability and values, starts to look like a pattern. Hashimoto won't say where Ghostty is going. He says he'll share details in the coming months.
