Mitchell Hashimoto, GitHub’s 1,299th user and creator of Vagrant and the Ghostty terminal emulator, has announced he’s migrating Ghostty away from GitHub after 18 years of near-daily use.
The decision wasn’t impulsive. Hashimoto kept a month-long journal tracking GitHub outages and found almost every single day had some kind of disruption blocking his work. On the day he wrote the post, GitHub Actions had already been down for two hours. “I can’t code with GitHub anymore,” he wrote. “I’m sorry. After 18 years, I’ve got to go.”
He links the reliability decline to Microsoft’s AI-driven changes to the platform, though he doesn’t spell out exactly what he means by that. Personal projects will stay on GitHub, but Ghostty — his main serious project — is moving. A read-only mirror will remain at the current GitHub URL so existing links don’t break.
Where Ghostty is actually going hasn’t been decided yet. Hashimoto says he’s evaluating both commercial and open-source alternatives and will share details in the coming months.
He’s not ruling out a return. But he’s clear that it would take real, demonstrated improvements — not announcements or roadmap promises.

Collections

Mitchell Hashimoto, creator of Ghostty and Vagrant, is migrating the Ghostty terminal emulator off GitHub after documenting near-daily outages over a month. He cites GitHub Actions downtime and broader reliability issues he attributes to Microsoft's AI-driven platform changes. Personal projects will remain on GitHub, but a read-only mirror will replace the active Ghostty repo. He hasn't chosen a destination yet, evaluating both commercial and open-source alternatives, and hasn't ruled out returning if GitHub demonstrates real improvements.

Ghostty is leaving GitHub over reliability concerns

As a disgruntled GitHub user, I think he made a reasonable decision.

This one hits differently because Mitchell is not a casual GitHub user. If someone who has used the platform almost daily for 18 years says “I can’t code with GitHub anymore,” that is not rage quitting. That is a reliability signal. For serious projects, developer infrastructure is not just a convenience layer. It is part of the build system, release process, contributor workflow, and trust chain. When outages become normal, migration stops being ideological and becomes operational risk management.

GitLab, Codeberg, Forgejo, Gitea? There are other options depending on your requirements. Most of which will meet your integration requirements. Or your need to self-host if desired.

As a noob, ALL the other options suck.

Many professionals may leave but the problem is that the GitHub will stay the defaul option for most of people even though GitLabs serves everything as GitHub.