Ghostty is leaving GitHub

The News

Mitchell Thompson, creator of Ghostty, a popular command-line terminal emulator known for its performance and features, announced on April 29, 2026, that he will be discontinuing its development and removing the project from GitHub [1]. This decision marks a significant shift for the open-source community, particularly among developers who rely on Ghostty for its speed and customization options. The announcement, made via Thompson’s personal blog, cites increasing costs associated with maintaining the project, particularly in the face of GitHub’s recent policy changes regarding AI usage and associated infrastructure expenses [1]. The move is abrupt, leaving many users scrambling to find alternatives, and raises questions about the sustainability of open-source projects in an era of increasingly complex software and rising computational demands [1]. Thompson has not specified a timeline for the repository removal, but indicated that it will occur at an unspecified future date [1].

The Context

Ghostty’s departure from GitHub is inextricably linked to a confluence of factors, primarily revolving around the evolving economics of AI development and GitHub’s response to those pressures. Ghostty, while not directly reliant on AI in its core functionality, benefits from a community that often utilizes AI-powered tools like GitHub Copilot within the terminal environment. The recent announcement by GitHub that it will begin charging Copilot users based on actual AI usage, starting June 1st [2], represents a significant change in the platform's revenue model. This shift is intended to "better align pricing with actual usage" and address the rising costs of providing AI computing resources [2]. GitHub Copilot, a code-assistant powered by OpenAI’s models, has seen surging demand, placing a strain on available resources and necessitating a change in billing practices [2].

This economic pressure on GitHub is further contextualized by the broader restructuring of Microsoft and OpenAI’s partnership [3]. The amended agreement dismantles previous exclusivity clauses, allowing OpenAI to offer its models on competing cloud platforms like Amazon Web Services (AWS) and Google Cloud [3]. This shift reflects a fundamental re-evaluation of the commercial AI landscape, moving away from a tightly controlled, vertically integrated model towards a more open and competitive ecosystem [3]. The original agreement involved significant financial commitments: Microsoft initially invested $1 billion in OpenAI, with further commitments totaling $13 billion, and a potential total investment of $50 billion contingent on OpenAI's performance [3]. The loosening of this agreement signals a potential reduction in Microsoft’s direct financial stake and a greater emphasis on OpenAI’s ability to generate revenue independently [3].

The timing of Ghostty’s departure also coincides with a broader discussion around the profitability of AI ventures [4]. Despite the hype surrounding generative AI, many companies are struggling to translate AI research into sustainable revenue streams. OpenAI, despite its valuation exceeding $134 billion, is reportedly operating with a profit margin of only 3% [4]. This "AI profit problem" is exacerbated by the high costs associated with training and deploying large language models (LLMs), which require significant computational resources and specialized expertise [4]. The Musk vs. Altman legal showdown, currently underway, further underscores the tensions surrounding OpenAI’s governance and its transition to a for-profit entity, with the court potentially ruling on whether the company can exist as a for-profit enterprise [4].

Finally, a recent critical security vulnerability (CVE-2026-3854) discovered in GitHub itself, allowing for remote code execution via a single Git push, adds another layer of complexity. While not directly caused by Ghostty’s development, this vulnerability highlights the inherent risks associated with relying on a centralized platform like GitHub for code management and distribution, potentially increasing operational costs for open-source maintainers. The vulnerability’s severity, coupled with the increased scrutiny on GitHub's security practices, likely contributed to the overall financial burden Thompson cited in his announcement [1].

Why It Matters

Ghostty’s departure has a cascading impact on several stakeholders within the developer ecosystem. For developers themselves, the immediate consequence is the loss of a high-performance terminal emulator known for its responsiveness and customization capabilities [1]. Many developers, particularly those working with computationally intensive tasks or requiring precise control over their terminal environment, will need to migrate to alternative solutions, potentially introducing technical friction and impacting productivity [1]. The search for replacements will likely lead to increased adoption of other terminal emulators, such as iTerm2 or Alacritty, but these alternatives may not perfectly replicate Ghostty’s unique feature set [1].

The impact on enterprises and startups is more nuanced. While individual developers may experience minor inconveniences, organizations that rely on Ghostty for critical workflows may face more significant disruptions [1]. The cost of migrating to alternative tools, retraining employees, and adapting existing scripts and configurations can be substantial, particularly for companies with large development teams [1]. Furthermore, the incident highlights the precariousness of relying on open-source projects maintained by individuals, as the sudden discontinuation of a critical tool can disrupt business operations [1]. The move also underscores the increasing cost of maintaining open-source projects, especially those that indirectly benefit from AI-powered tools like GitHub Copilot [2].

The winners in this situation are likely to be alternative terminal emulator developers, who now have an opportunity to capture Ghostty’s user base [1]. Companies offering cloud-based development environments or integrated development environments (IDEs) may also benefit, as developers seek more comprehensive solutions that reduce reliance on individual tools [1]. Conversely, GitHub faces a potential loss of developer goodwill and a possible erosion of its position as the dominant code hosting platform [1]. The incident serves as a cautionary tale for other open-source maintainers, highlighting the challenges of sustaining projects in an environment where infrastructure costs are rising and platform dependencies are becoming increasingly complex [1]. The Microsoft/qlib repository, with 38,643 stars, demonstrates the continued reliance on Python-based tools within the developer ecosystem, a dependency that Ghostty's departure could indirectly impact.

The Bigger Picture

Ghostty’s exit from GitHub is symptomatic of a larger trend: the increasing commoditization and commercialization of open-source software. While open-source remains a cornerstone of the software development industry, the traditional model of volunteer-driven maintenance is proving increasingly unsustainable in the face of rising infrastructure costs and the demands of enterprise adoption [1]. This trend is accelerating as AI technologies become more deeply integrated into the development workflow, creating a complex web of dependencies and financial obligations [2]. GitHub's shift to usage-based billing for Copilot is a direct response to this pressure, but it also creates a disincentive for open-source projects that rely on GitHub’s infrastructure [1, 2].

Competitors are responding to this shift in various ways. GitLab, for example, has historically positioned itself as a more developer-friendly alternative to GitHub, offering more generous free tiers and a greater emphasis on open-source contributions. Bitbucket, another code hosting platform, is also vying for developer mindshare, offering similar features and pricing models. The legal battle between Musk and Altman, and the potential ruling on OpenAI's for-profit status, could further reshape the AI landscape, influencing the pricing and accessibility of AI-powered tools [4]. The fact that OpenAI is now free to sell its models on AWS and Google Cloud [3] suggests a move towards a more decentralized AI infrastructure, potentially reducing the reliance on proprietary platforms like GitHub [3].

Over the next 12-18 months, we can expect to see increased experimentation with alternative open-source licensing models, decentralized code hosting platforms, and community-funded development initiatives [1]. The incident will likely spur a renewed focus on the long-term sustainability of open-source projects and the development of more robust funding mechanisms [1]. The 97% of OpenAI’s revenue that comes from Microsoft [4] highlights the reliance on large corporate partnerships, a model that may prove vulnerable to shifts in strategic priorities [4].

Daily Neural Digest Analysis

The mainstream narrative surrounding Ghostty’s departure focuses on the technical inconvenience for developers – the loss of a preferred terminal emulator [1]. However, the deeper story is about the erosion of the open-source ethos under the weight of commercial pressures. The incident is a stark reminder that even the most beloved open-source projects are not immune to the forces of market economics [1, 2]. GitHub’s move to usage-based billing, while understandable from a business perspective, inadvertently creates a two-tiered system where projects that heavily rely on AI-powered tools are penalized [1, 2].

The hidden risk lies in the potential for a chilling effect on open-source contributions. If maintainers perceive that the costs of maintaining a project outweigh the benefits, they may be less likely to contribute their time and expertise, leading to a decline in the overall quality and diversity of open-source software [1]. The vulnerability in GitHub itself further exacerbates this risk, highlighting the security and operational burdens faced by open-source maintainers.

Ultimately, the question remains: how can the open-source community adapt to a world where AI is ubiquitous and infrastructure costs are rising? Can new funding models, decentralized platforms, or collaborative governance structures provide a sustainable path forward? The answer will shape the future of software development and the accessibility of technology for generations to come [1].

---

References

[1] Editorial_board — Original article — https://mitchellh.com/writing/ghostty-leaving-github

[2] Ars Technica — GitHub will start charging Copilot users based on their actual AI usage — https://arstechnica.com/ai/2026/04/github-will-start-charging-copilot-users-based-on-their-actual-ai-usage/

[3] VentureBeat — Microsoft and OpenAI gut their exclusive deal, freeing OpenAI to sell on AWS and Google Cloud — https://venturebeat.com/technology/microsoft-and-openai-gut-their-exclusive-deal-freeing-openai-to-sell-on-aws-and-google-cloud

[4] MIT Tech Review — The Download: Musk and Altman’s legal showdown, and AI’s profit problem — https://www.technologyreview.com/2026/04/28/1136479/the-download-musk-altman-openai-trial-ai-profit-problem/