Developing Story
Ghostty – GitHub Departure (2026)
Ghostty, the open-source terminal emulator by HashiCorp co-founder Mitchell Hashimoto, announced it is leaving GitHub, adding a high-profile data point to the growing developer backlash against GitHub centralization. (mitchellh.com, 2026) The move may influence other open-source maintainers to reconsider platform dependency and accelerate adoption of GitHub alternatives.
Importance: 58%Confidence: 75%Mentions: 1Updated: April 30, 2026
## Overview
Ghostty, an open-source terminal emulator developed by Mitchell Hashimoto, announced it is leaving GitHub as its primary hosting and development platform. (mitchellh.com, 2026) The move represents a notable signal in the growing developer discourse around GitHub centralization and platform dependency.
## Background
- Ghostty is a widely followed open-source terminal emulator that attracted significant developer attention following its launch, partly due to Hashimoto's prominence as a co-founder of HashiCorp.
- The decision to leave GitHub follows a broader pattern of developer tools and projects reconsidering centralized platform dependency, particularly following GitHub's controversial policy changes and Microsoft's ownership.
## Significance
- Hashimoto's decision carries weight given his influence in the developer tools community and his prior experience building infrastructure software at scale.
- The departure is consistent with the broader narrative of developer backlash against GitHub centralization, particularly among open-source maintainers concerned about platform lock-in, policy enforcement, and data use.
- The move may accelerate consideration of alternatives (Codeberg, Forgejo, self-hosted Gitea) among open-source projects.
## Connections
This development connects to existing tensions around Microsoft's stewardship of GitHub, including the VeraCrypt account termination conflict documented elsewhere in this system.
## Open Questions
- The specific alternative platform or hosting approach Ghostty is migrating to was not detailed in available sources at time of writing. (mitchellh.com, 2026)
- Whether the departure is partial (e.g., moving issue tracking while retaining code mirroring) or complete has not been confirmed.