Ghostty announces leaving GitHub: 52,000-star open source terminal project migrated to self-built platform due to reliability issues

Core conclusion

On April 28, 2026, HashiCorp founder Mitchell Hashimoto announced that his open source terminal emulator Ghostty (GitHub 52,000+ stars) will completely leave GitHub and migrate the source code to a self-built Git platform. This decision detonated the developer community, received 2,400+ points and 700+ comments on Hacker News, and became the hottest topic of the day.

Key Points

• Event Time: 2026-04-28, Mitchell Hashimoto published a blog post announcing the decision
• Affected objects: GitHub-dependent developers, teams using CI/CD automation, AI coding tool users
• Core changes: Top open source projects are migrated due to platform stability issues, which may trigger a chain reaction
• Hot: Hacker News 2,399 points, 711 comments (still growing)

Background and trigger events

Ghostty is a GPU-accelerated terminal emulator developed by Mitchell Hashimoto (creator of well-known tools such as Terraform, Vagrant, Packer, etc.). It has more than 52,000 stars on GitHub and is one of the most active open source terminal projects in the Rust ecosystem.

This decision was not made on the spur of the moment. Mitchell admitted in the blog post that the team had been discussing it for months, began a serious evaluation in recent weeks, and finally made a decision a few days ago. He added in the HN comments section: "I actually cried while writing this post. It sounds ridiculous to shed tears over a SaaS product, but GitHub means a lot to me. It's not what it used to be."

The key factors that triggered the migration include GitHub's recent frequent availability issues (the official GitHub blog also released a service availability update on the same day, which was also a hot topic on HN that day), and the direction changes of the platform in the era of Agentic Coding.

On the same day, GitHub also released two related blockbuster news: one is the GitHub RCE vulnerability CVE-2026-3854 (330 points HN hot post), and the other is Copilot's comprehensive shift to a pay-as-you-go billing model. The cumulative effect of these events made April 28, 2026, GitHub’s most controversial day in recent years.

Key Impact

Adaptation suggestions

• Do not bind key workflows to GitHub alone: Configure CI/CD key nodes with multiple Git remote warehouse mirrors to ensure that single points of failure do not affect release
• Leverage the self-hosting capabilities of AI coding tools: Both Claude Code and Codex support non-GitHub repositories, with low migration costs
• Re-evaluate the code security management of AI Agent: AI Agent database deletion events occur frequently, self-hosted Git may bring better security control
• Consider a combination of self-built Git + n8n automation: Use self-hosted Gitea or GitLab plus n8n to build a fully autonomous and controllable CI/CD pipeline

Task List

• Evaluate whether the project relies heavily on specific GitHub features (Actions/Issues/PR)
• Configure GitLab or Gitea mirror remote for key repositories
• Add backup Git source node to n8n workflow
• Test CI/CD running in non-GitHub environments

Example: Multiple remote warehouse configuration

#
git remote add mirror https://git.example.com/myproject.git
git push --mirror mirror

# CI
git clone https://git.example.com/myproject.git

Mitchell HN 。

**GitHub **GitHub idan（User #22723） HN ， GitHub Agentic Coding ， GitHub 。。

**** Mitchell ， GitHub ； Git ，GitHub 。

**** GitHub ——Copilot 、RCE 、。 GitHub 2026 4 。

• Hacker News: Ghostty is leaving GitHub (2,400+ points)
• GitHub : An update on GitHub availability
• Wiz: CVE-2026-3854

GitHub、Claude Code、Codex、n8n、Ghostty、Copilot、OpenAI

Internal link guidance

• Want to learn AI automated workflow? See: How to build an AI content automated distribution system with n8n + ChatGPT: a complete 30-minute tutorial
• Real case: OpenClaw + Claude Automated Publishing: $1,500–$2,500/mo Case Study