Ghostty Terminal Emulator Leaves GitHub After Month of Daily Outages

Mitchell Hashimoto, GitHub user #1299 since February 2008, is pulling the Ghostty terminal emulator project off GitHub after 18 years of daily use, citing outages that have disrupted work "almost every day" for the past month. The creator of Vagrant documented a ~2-hour GitHub Actions outage that blocked pull request reviews and a major Elasticsearch infrastructure failure on April 27, 2026, among multiple separate incidents. For enterprises running CI/CD pipelines (automated testing and deployment systems), issue tracking, and code review through GitHub, the departure of a high-profile open source project signals reliability concerns that translate directly to lost developer hours and deployment delays.

The announcement marks a rare public exit from the platform that has anchored the open source ecosystem for nearly two decades. Hashimoto's first major project, Vagrant, launched on GitHub when he was 20 years old with the hopeful aside "maybe GitHub will hire me if it's good!" Now, after watching GitHub Actions and related infrastructure fail repeatedly during critical work windows, the Ghostty team is migrating incrementally to an as-yet-unannounced alternative while maintaining a read-only mirror at the current GitHub URL.

What's new

Ghostty will leave GitHub over the coming months following a month-long journal of infrastructure failures that repeatedly blocked development work. Recent incidents include a ~2-hour GitHub Actions outage that prevented pull request reviews and a large-scale Elasticsearch outage (a search engine component powering issue and code search) on April 27, 2026, both part of a pattern Hashimoto described as "almost every day" disruptions during the past month. The team has been in discussions with multiple providers but has not yet disclosed the migration destination.

Ghostty, an open source terminal emulator, depends heavily on GitHub's collaboration features. Pull requests, issue tracking, and continuous integration workflows form the backbone of modern open source development, and when those systems fail for hours at a time, entire teams sit idle. Hashimoto clarified that the problem is not Git itself (the version control software that runs locally) but "the infrastructure we rely on around it: issues, PRs, Actions, etc." Git repositories can exist anywhere; the collaborative tooling layer ties projects to platforms like GitHub.

The migration will proceed incrementally to remove all dependencies on GitHub infrastructure. A read-only mirror will remain at the current Ghostty URL to preserve links, search engine indexing, and community access to historical discussions. This balances continuity for existing users with the operational need to move critical workflows off a platform experiencing frequent downtime. The Ghostty team has not provided a specific timeline, noting only that the decision was finalized "this week."

Why it matters

GitHub Actions outages directly translate to developer productivity loss at enterprise scale. When automated testing pipelines, deployment workflows, and code review processes halt for two hours, engineering teams cannot safely merge code, validate changes, or ship releases. For organizations running hundreds or thousands of pull requests per day, a single extended outage cascades into backlog buildup, delayed feature launches, and increased operational risk as teams either wait for infrastructure to recover or attempt manual workarounds that bypass safety checks.

The April 27, 2026 Elasticsearch outage represents a single point of failure in a platform that millions of developers depend on for mission-critical workflows. Elasticsearch powers search functionality across issues, pull requests, and code repositories, meaning an outage in that component can render entire swaths of the platform unusable even if Git operations continue functioning. Hashimoto's month-long journal showing near-daily disruptions suggests the April 27 incident was part of a broader reliability pattern rather than an isolated event.

The distinction between Git and GitHub infrastructure is critical for enterprise decision-makers evaluating platform risk. Git is distributed by design, meaning every developer has a complete copy of the repository history locally, so losing access to a hosting platform does not destroy code. However, modern software development workflows depend on centralized collaboration tools: issue trackers, pull request systems, and continuous integration pipelines. When those systems fail, distributed version control offers no safety net.

Hashimoto's departure carries weight because of his 18-year tenure and status as GitHub user #1299, placing him among the earliest adopters when the platform launched in 2008. His open source projects, including Vagrant, have shaped developer tooling for more than a decade, and his firsthand account of reliability erosion provides credibility that generic uptime statistics cannot match. If a power user with deep platform expertise chooses to migrate despite the operational cost of switching platforms, it signals problems severe enough to outweigh the friction.

Competitive Landscape

Hashimoto's announcement names "multiple providers, both commercial and FOSS" but does not yet name the destination. The realistic candidate set is narrow and well-characterized:

Codeberg — non-profit Forgejo-based forge run by Codeberg e.V. (registered German non-profit, "eingetragener Verein") on dedicated hardware in Berlin with backup via Hetzner and netcup. Free for FOSS projects, donation-funded, community-governed. The closest match to a high-profile FOSS project's stated values.
sourcehut (sr.ht) — Drew DeVault's paid alternative, $5/$10/$15 per month with all tiers feature-identical. Email-driven git workflow, no JavaScript required. New-customer pricing was raised in January 2026; existing users grandfathered.
GitLab.com — the largest mature GitHub alternative with built-in CI/CD and self-host parity. Free tier plus paid plans. GitLab.com's public status tracker recorded 39 incidents (5 major, 34 minor) in the 90 days preceding May 2026, with median duration of about 2h 36m — concrete proof that "GitHub alternative" doesn't mean "no outages," just transparent incident reporting.
Forgejo (self-hosted) — community fork of Gitea after governance shifted to Gitea Ltd. in 2022. AGPL/GPL-3.0, first mainstream forge to ship ForgeFed/ActivityPub federation. Self-hosting means uptime is operator-controlled.
Gitea Cloud — paid hosted version of the original lightweight forge. Useful as a low-friction commercial option that runs the same software thousands of self-hosted instances already use.

Drew DeVault, founder of sourcehut and one of the most-cited public voices against forge centralization, has argued the structural case in his January 2021 essay "Use open platforms — or else." The thesis lands harder when a HashiCorp co-founder and Vercel board member is the one acting on it: in March 2026, Vercel appointed Hashimoto to its Board of Directors, citing his role as co-founder of HashiCorp and creator of Terraform. HashiCorp itself was acquired by IBM in 2024 in a deal valued at $6.4 billion. Hashimoto's exit is not a small-project gesture — it is a signal from the kind of operator most likely to migrate other operators with him. FFmpeg's canonical repository has lived at git.ffmpeg.org with GitHub serving only as a mirror for years; high-profile FOSS projects keeping primary infrastructure off GitHub is precedent, not precedent-setting.

What's next

The Ghostty team will announce the migration destination in the coming months after completing discussions with alternative platform providers. Both commercial offerings and free and open source software (FOSS) solutions are under consideration, indicating the team is weighing trade-offs between managed reliability, cost, feature parity, and control over infrastructure. The decision to maintain a read-only GitHub mirror suggests the team recognizes the value of preserving community links and historical context even as active development moves elsewhere.

The broader implications for GitHub depend on whether Ghostty's departure represents an isolated case or the leading edge of a larger migration wave. GitHub has not issued a public statement addressing the outage frequency Hashimoto documented, and official uptime metrics or service-level commitments for GitHub Actions are not prominently disclosed on the platform's homepage or status pages. Without transparency into historical reliability trends, enterprise customers evaluating platform risk have limited data to assess whether recent outages reflect temporary issues or systemic degradation.

Competition in the developer platform space has intensified as GitLab, Bitbucket, and emerging alternatives compete on features including integrated CI/CD, security scanning, and AI-assisted coding. GitHub touts push protection that stopped 8.3 million secret leaks in the past 12 months and reports from Duolingo claiming a 25% developer speed boost using GitHub Copilot, but reliability concerns may drive project migrations if competitors demonstrate stronger uptime track records. For now, the exodus of a single high-profile project serves as a public test case: if Ghostty's migration succeeds without significant productivity loss, it establishes a playbook other teams may follow if GitHub's reliability does not improve.

GitHub's own success created the dependency that makes outages so painful. When a single service hosts the majority of the world's open source collaboration, infrastructure failures ripple across the entire software ecosystem. Hashimoto's departure is less a rejection of centralized collaboration than a demand for infrastructure reliability that matches the mission-critical role GitHub has come to play. The question for Microsoft is whether operational improvements arrive before more projects conclude that the cost of staying exceeds the cost of leaving.

For a solo open-source maintainer running CI on every pull request, GitHub's near-daily two-hour outages cost an unbudgeted 8-12 review-cycles per week of build-rerun overhead — every affected PR re-runs the full test matrix from scratch when Actions recovers. At sourcehut's $5/month entry tier or Codeberg's free FOSS hosting, the migration cost-benefit equation flips at roughly four such weeks. The infrastructure rebuild — moving issue tracker, CI configuration, and webhook integrations — is real work, but Hashimoto's read-only-mirror strategy preserves the inbound link graph (search rankings, third-party references, historical discussion permalinks) that usually anchors maintainers to a platform long after the operational case for staying has dissolved.

-- Aria Lin, Enterprise Technology Analyst

Sources: Mitchell Hashimoto — Ghostty Is Leaving GitHub · Drew DeVault — Use open platforms or else · Codeberg · sourcehut pricing · Forgejo · GitLab Status