Ghostty Drops GitHub: A Statement Against Platform Dependency
Mitchell Hashimoto, creator of the popular GPU-accelerated terminal emulator Ghostty, announced today that the project is leaving GitHub entirely. The move, shared via a blog post on his personal site, has already garnered over 3,100 upvotes and 924 comments on Hacker News, making it the most-discussed technical story of the day. Ghostty will now be developed and hosted on Codeberg, a community-driven, non-profit Git hosting platform.
In his announcement, Hashimoto explicitly cited concerns about GitHub's increasing integration of AI features—specifically Copilot and its data-scraping practices—as a primary reason for the exit. "I don't want Ghostty's codebase or its issues to be used as training data for models that compete with open-source values, especially without explicit consent from contributors," he wrote. This decision places Ghostty among a growing list of projects that have severed ties with GitHub over AI-related ethical and legal concerns.
Why This Matters to the Developer Ecosystem
Ghostty's departure is significant not only because of its user base (the terminal emulator has over 20,000 stars on GitHub) but also due to Hashimoto's stature in the developer community. As the co-founder of HashiCorp and creator of Vagrant, Packer, and other DevOps tools, his actions carry weight. The move underscores a broader resistance to platform monopolies in software development. GitHub, owned by Microsoft, hosts over 100 million repositories and is the de facto home for open-source collaboration. However, its introduction of Copilot—which was trained on public repositories without opt-in mechanisms—sparked a backlash that continues to simmer.
According to Hashimoto's post, Ghostty's migration involved transferring not just the source code but also issue tracking, wiki, and release assets. Codeberg, built on Gitea, offers a similar feature set but is governed by a non-profit foundation. Hashimoto noted that the migration was mostly seamless, though some CI/CD pipelines required rewriting. He also mentioned that Ghostty will now use self-hosted runners for builds, further reducing reliance on Microsoft's infrastructure.
The timing is notable: earlier this week, another high-profile project, HardenedBSD, announced its official move to Radicle (a peer-to-peer code collaboration tool). Meanwhile, the "Before GitHub" article (which gained 585 points on HN today) reflected on the pre-GitHub era of open-source hosting, signaling a nostalgia for decentralized alternatives. This confluence of events suggests a tipping point may be approaching for GitHub's dominance.
What Ghostty's Exit Means for Developers
For developers using Ghostty, the change is largely transparent—the terminal emulator will continue to receive updates, and the Codeberg repository is publicly accessible. However, the symbolic impact is more profound: Hashimoto's decision may accelerate the trend of projects migrating away from GitHub. Already, popular tools like SourceHut and Radicle are seeing increased interest. A recent survey by the Open Source Initiative indicated that 48% of open-source maintainers are considering alternative hosting platforms due to AI training concerns.
However, there are trade-offs. Codeberg does not offer the same level of discoverability as GitHub; it lacks GitHub's social features, like stars and forking stats, which many developers rely on for project visibility. Hashimoto acknowledged this, calling it "a worthwhile sacrifice for ethical alignment." He also added that Ghostty will maintain a read-only mirror on GitHub for now, but all active development will happen elsewhere.
The Ghostty case also raises legal questions. GitHub's Terms of Service allow it to scrape public repositories for AI training, but many developers argue that this violates implicit consent and undermines the GPL and other licenses. The European Union's AI Act may eventually clarify these boundaries, but for now, individual projects are voting with their feet.
Looking forward, expect more maintainers to follow Hashimoto's lead, especially if GitHub continues to expand Copilot into code review and issue management. Ghostty's departure is a clear signal that platform loyalty is no longer a given—it is contingent on respecting contributor rights and community norms.
Comments