91Trust
Verified
🔍 Web Verified
Mitchell HashimotoonMastodon7h ago
Ghostty is leaving GitHub. I'm GitHub user 1299, joined Feb 2008. I've visited GitHub almost every single day for over 18 years. It's never been a question for me where I'd put my projects: always GitHub. I'm super sad to say this, but its time to go. https://mitchellh.com/writing/ghostty-leaving-github
Trust Metrics
95
92
85
85
Accuracy95%
Framing92%
Context85%
Tone85%
Analysis Summary
Mitchell Hashimoto, GitHub user since 2008 and creator of Vagrant and Ghostty, announced he's moving the Ghostty project off GitHub after 18 years due to repeated outages blocking his ability to work. He's keeping his personal projects on GitHub but moving Ghostty incrementally to another provider (commercial or open-source, still being evaluated), with a read-only mirror remaining at the current URL. The decision was finalized this week after months of planning — the timing overlaps with a major GitHub outage on April 27 but Hashimoto says the two are unrelated.
Claims Analysis (6)
“Ghostty is leaving GitHub”
Mitchell Hashimoto published detailed blog post announcing Ghostty's departure from GitHub on April 28, 2026. Corroborated by El Ecosistema Startup coverage.
“Mitchell Hashimoto is GitHub user 1299, joined Feb 2008”
Stated directly in the linked article and in Hashimoto's post history. GitHub user ID 1299 is verifiable primary information.
“Hashimoto has visited GitHub almost every single day for over 18 years”
Post says 'almost every single day' with 'handful of exceptions' — this is self-reported personal practice claim, not independently verifiable but internally consistent.
“GitHub has had frequent outages negatively impacting work, with almost every day in the past month marked by an outage”
Hashimoto's personal journal tracking outages is not independently verifiable. The April 27, 2026 outage is real, but claim of 'almost every day' failures rests on personal observation.
“A GitHub Actions outage blocked PR review for approximately 2 hours on the day the post was written”
Specific incident described as occurring on post date (April 28, 2026). While impact duration is subjective, GitHub Actions outages on or near this date are consistent with known service issues.
“The timing with the April 27, 2026 GitHub outage is coincidental; the decision to leave was made months prior”
Hashimoto explicitly states the blog post was written over a week before the decision was finalized, and plans were in development for months. This is self-reported and internally consistent.
Was this analysis helpful?
Try ClearFeed free →