Ghostty Leader Announces Departure from GitHub
The main maintainer of Ghostty stated that frequent failures and instability of GitHub have severely impacted development work. He will migrate all heavy development to self-hosted services, retaining GitHub only as a code repository.
This developer has over 50,000 followers on GitHub and is a heavy user, making daily submissions. The most affected features are Actions, PR, and Issues, leading to frequent interruptions in code reviews and CI processes.
Market mechanisms indicate that developers and AI engineering teams are accelerating the shift from GitHub's core services to more stable, self-hosted, or AI-optimized platforms. GitHub is under pressure in high-frequency development scenarios, while new platforms providing reliable CI/CD, PR reviews, and agent-friendly infrastructure benefit, with capital concentrating on more reliable code collaboration tools for the AI era.
Source: Public Information
ABAB AI Insight
Ghostty's leader, as a heavy user of GitHub, has long relied on its ecosystem for daily submissions, PR reviews, and CI. This public departure directly reflects that GitHub's service stability issues have reached the core developers' bottom line by 2026, especially as frequent failures in Actions and PR systems have impacted AI agent-driven development processes.
In terms of capital pathways, developers are migrating core workloads to self-hosted Git services or emerging platforms, shifting resources from CI/CD reliant on GitHub Actions to local/private deployments. The strategic goal is to avoid disruptions to AI Agent workflows caused by Microsoft's infrastructure instability while opening a window for new Git services better suited for natural language-driven development and multi-agent collaboration.
Similar cases include several well-known open-source maintainers transitioning to self-hosted or SourceHut due to GitHub's stability issues in 2024-2025, as well as the reverse trend of early developers migrating from Subversion to GitHub. Currently, GitHub is under pressure to transform from a developer's preferred platform to facing reliability challenges in the AI era.
Essentially, this represents a technological replacement: the traditional centralized workflow of GitHub is being replaced by high-reliability, self-hosted, or agent-native Git services in the AI era. The mechanism is driven by the stringent demands of AI-driven continuous integration and code review for low latency and high availability, where frequent failures lead to developer attrition, shifting pricing power from Microsoft GitHub to the next generation of code collaboration platforms that are more stable and AI-friendly (supporting parallel PRs, automated reviews, etc.), while accelerating the reconstruction of developer infrastructure from general SaaS to intelligent productivity-specific systems.