Ghostty terminal emulator project ends 18-year GitHub tenure amid infrastructure reliability concerns

The Ghostty terminal emulator project has announced it will cease hosting its primary repository on GitHub, ending an eighteen-year relationship that saw the maintainer, Mitchell Hashimoto, use the platform daily for his personal and professional work. The decision comes after a period of frustration regarding the reliability of GitHub's infrastructure, which has increasingly hindered the team's ability to conduct serious work, review pull requests, and ship software updates.

Hashimoto, who has publicly expressed anger over the platform's performance, noted that persistent outages have made the site unusable for critical development tasks on a near-daily basis. While the project team acknowledges the deep personal connection to the platform, the inability to access features such as GitHub Actions, issues, and pull requests has forced a reassessment of their operational dependencies. The final decision to migrate was made this week, though the blog post announcing the move was drafted over a week prior to a significant outage on 27 April 2026.

To ensure continuity during the transition, the project team plans to maintain a read-only mirror of the repository on GitHub at the current URL. This measure allows the community to continue viewing code and history while the primary active development moves to a new location. The migration strategy is designed to be incremental, aiming to remove all dependencies on GitHub's centralised infrastructure without immediately displacing Hashimoto's other personal projects, which will remain on the platform for the time being.

The team is currently in discussions with multiple potential hosting providers to establish a more robust and independent infrastructure. These options include both commercial services and free or open-source software (FOSS) solutions, reflecting a desire for a platform that prioritises uptime and developer productivity. The specific timeline for the full migration remains undefined, as the group finalises negotiations with these prospective hosts.

Hashimoto clarified that the move does not signal a rejection of Git itself, which remains a distributed system, but rather a necessary shift away from the centralised services that surround it. The issue lies with the infrastructure supporting issues, pull requests, and automation tools, which have failed to meet the demands of a high-stakes open-source project. This distinction is crucial as the team seeks a solution that supports the rigorous workflow required to maintain a modern terminal emulator.

While the destination for the project's future hosting has not been confirmed, the focus remains on creating an environment where the maintainers and the open-source community can work without the constant interruption of platform failures. The project team will share further details regarding the new hosting arrangements in the coming months as discussions with providers progress.