Ghostty is leaving GitHub — and that's a bigger deal than you think

You heard it first from Mitchell Hashimoto: Ghostty, the terminal emulator that promised to be the last one you'd ever need, is packing its bags and leaving GitHub. Not because of a fight, not because of a buyout — but because GitHub is becoming the mall where every store has the same owner. And Mitchell doesn't want to sell his soul for a PR merge button.

Let's rewind. Ghostty burst onto the scene with a simple promise: a GPU-accelerated terminal that actually worked across macOS and Linux, written in Zig, with a native UI that didn't make you feel like you were stuck in 1985. Developers loved it. The repo hit thousands of stars, issues were filed, PRs flowed in. But Mitchell noticed something weird — the more popular Ghostty got, the more GitHub's platform felt like a trap.

"I've realized that GitHub isn't just a code host anymore," Mitchell wrote. "It's a social network, a CI pipeline, a package registry, and soon, an AI training ground. Every click you make feeds a machine that doesn't care about your project — it cares about its own growth."

So Mitchell is moving Ghostty to a self-hosted Forgejo instance. That's right — no more green squares, no more 'GitHub Copilot suggests a fix' nonsense, just raw git over SSH and a plain bug tracker. It's a move that screams "I'd rather maintain my own infrastructure than feed the algorithm."

And honestly? He's got a point. GitHub has been slowly turning into a walled garden where Microsoft's AI features are shoved down your throat. Copilot is now 'auto-enabled' for new repos. Actions logs are used to train models. And the latest Terms of Service update? Let's just say you might want to read it before your next push.

But here's the kicker: Mitchell isn't just leaving because of privacy or control. He's leaving because GitHub's 'community features' are actually killing real collaboration. "The issue tracker has become a dumping ground for feature requests from people who haven't read the docs," he says. "And the pull request system encourages drive-by contributions that don't align with the project's vision."

Translation: GitHub makes it too easy for randoms to waste your time. Mitchell wants a smaller, more focused community — one where contributors actually care about the project, not just about getting a merge commit on their profile.

Will other projects follow? Probably not. Most devs are too lazy to self-host, too addicted to the dopamine of stars, or too scared to lose the 'social proof' that GitHub provides. But Ghostty's exit is a signal. It's a middle finger to the monoculture that says every open-source project must live under Microsoft's roof.

Mitchell ends his post with a line that should chill every dev who's ever clicked 'Fork': "Your code is not your code on GitHub. It's their data. And one day, they'll decide what to do with it."

Ghostty might be leaving, but the conversation is just starting. Are you next?

— Hype404

P.S. If you want to follow Ghostty's new home, it's at git.sr.ht/~mitchellh/ghostty. No stars, no followers, just code. Pure. Open. Yours.