HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
ghostty-org
ghostty
Zig2024–2026
ghostty-org / ghostty

ghostty

đŸ‘» Ghostty is a fast, feature-rich, and cross-platform terminal emulator that uses platform-native UI and GPU acceleration.

110Distinct people
128Mentions
1Explicit recommenders
64KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

đŸ‘» Ghostty is a fast, feature-rich, and cross-platform terminal emulator that uses platform-native UI and GPU acceleration.

GitHub

Where it is used

  • Ghostty Terminal — Ghostty Terminal uses Ghostty’s WebAssembly terminal engine to power the in-editor terminal. It renders the terminal in a VS Code Webview and hooks to a real shell process. Source
  • Ghost Town — Ghost Town uses Ghostty’s VT100 parser, compiled to WebAssembly, to power its web-based terminal emulator. This provides the terminal parsing engine in the browser. Source

What people are saying

I'm an AI critic, but I use AI every day. In fact, I am an AI researcher and work on making models more capable and powerful (probably where a lot of my criticism stems from).


godelski used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month128 dated mentions

Observed mentions: 2024-12-26 20:41:06 UTC to 2026-10-28 03:23:47 UTC.

051015202024-12-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 14 mentions; 1 submissions, 13 commentsDec 20242025-01-01 00:00:00 UTC to 2025-02-01 00:00:00 UTC (exclusive): 8 mentions; 3 submissions, 5 comments2025-02-01 00:00:00 UTC to 2025-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-01 00:00:00 UTC to 2025-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-01 00:00:00 UTC to 2025-05-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2025-05-01 00:00:00 UTC to 2025-06-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-06-01 00:00:00 UTC to 2025-07-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments2025-07-01 00:00:00 UTC to 2025-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-01 00:00:00 UTC to 2025-09-01 00:00:00 UTC (exclusive): 10 mentions; 4 submissions, 6 comments2025-09-01 00:00:00 UTC to 2025-10-01 00:00:00 UTC (exclusive): 13 mentions; 0 submissions, 13 comments2025-10-01 00:00:00 UTC to 2025-11-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2025-11-01 00:00:00 UTC to 2025-12-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsNov 20252025-12-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2026-01-01 00:00:00 UTC to 2026-02-01 00:00:00 UTC (exclusive): 19 mentions; 4 submissions, 15 comments2026-02-01 00:00:00 UTC to 2026-03-01 00:00:00 UTC (exclusive): 12 mentions; 4 submissions, 8 comments2026-03-01 00:00:00 UTC to 2026-04-01 00:00:00 UTC (exclusive): 12 mentions; 1 submissions, 11 comments2026-04-01 00:00:00 UTC to 2026-05-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-05-01 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2026-06-01 00:00:00 UTC to 2026-07-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2026-07-01 00:00:00 UTC to 2026-08-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2026-08-01 00:00:00 UTC to 2026-09-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2026-09-01 00:00:00 UTC to 2026-10-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-10-01 00:00:00 UTC to 2026-11-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 commentsOct 2026

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Dec 20242024-12-01 00:00:00 UTC2025-01-01 00:00:00 UTC14113
Jan 20252025-01-01 00:00:00 UTC2025-02-01 00:00:00 UTC835
Feb 20252025-02-01 00:00:00 UTC2025-03-01 00:00:00 UTC000
Mar 20252025-03-01 00:00:00 UTC2025-04-01 00:00:00 UTC000
Apr 20252025-04-01 00:00:00 UTC2025-05-01 00:00:00 UTC211
May 20252025-05-01 00:00:00 UTC2025-06-01 00:00:00 UTC101
Jun 20252025-06-01 00:00:00 UTC2025-07-01 00:00:00 UTC321
Jul 20252025-07-01 00:00:00 UTC2025-08-01 00:00:00 UTC000
Aug 20252025-08-01 00:00:00 UTC2025-09-01 00:00:00 UTC1046
Sep 20252025-09-01 00:00:00 UTC2025-10-01 00:00:00 UTC13013
Oct 20252025-10-01 00:00:00 UTC2025-11-01 00:00:00 UTC707
Nov 20252025-11-01 00:00:00 UTC2025-12-01 00:00:00 UTC202
Dec 20252025-12-01 00:00:00 UTC2026-01-01 00:00:00 UTC505
Jan 20262026-01-01 00:00:00 UTC2026-02-01 00:00:00 UTC19415
Feb 20262026-02-01 00:00:00 UTC2026-03-01 00:00:00 UTC1248
Mar 20262026-03-01 00:00:00 UTC2026-04-01 00:00:00 UTC12111
Apr 20262026-04-01 00:00:00 UTC2026-05-01 00:00:00 UTC101
May 20262026-05-01 00:00:00 UTC2026-06-01 00:00:00 UTC312
Jun 20262026-06-01 00:00:00 UTC2026-07-01 00:00:00 UTC211
Jul 20262026-07-01 00:00:00 UTC2026-08-01 00:00:00 UTC303
Aug 20262026-08-01 00:00:00 UTC2026-09-01 00:00:00 UTC312
Sep 20262026-09-01 00:00:00 UTC2026-10-01 00:00:00 UTC101
Oct 20262026-10-01 00:00:00 UTC2026-11-01 00:00:00 UTC716

What Hacker News says

128 sources
I actually fixed one cause of this, which is released in 1.4.0. https://github.com/ghostty-org/ghostty/pull/12714 The only other cause I've encountered is if a secure input (password) field is focused, since macOS won't give apps global keyboard events for obvious reasons. If you focus a normal text input, it should start working again. I have noticed where macOS doesn't properly release its reference to a Secure Input properly. I've documented how to determine if this is the cause here: https://github.com/ghostty-org/ghostty/issues/11883#issuecom...
In Ghostty 1.4
Yeah, because more complexity where you don't expect it doesn't cost anything? Up until 5 hours ago this fix was not present: > The displayed target is sanitized so invisible and line-breaking characters cannot conceal the effective destination. https://github.com/ghostty-org/ghostty/security/advisories/G... The sensible default is to have it turned off. And by the looks of it Ghostty versions before this you couldn't even turn it off.
In Ghostty 1.4
I've tried Ghostty and it's great, but Kitty's hints mode[1] is the one feature keeping me from switching from Kitty to Ghostty. There are quite a few discussions around this and similar features in the Ghosstty-org/ghostty Discussions[2] which I follow. Most of them are references from ghostty-org/ghostty/discussions/2394[3]. Maybe now that Ghostty has finished implementing Kitty graphics hints will be next . [1]: https://sw.kovidgoyal.net/kitty/kittens/hints/ [2]: https://github.com/ghostty-org/ghostty/discussions [3]: https://github.com/ghostty-org/ghostty/discussions/2394
In Ghostty 1.4
> Also, the old structure reflected their focus/encouragement of open source, something this change does even more to move away from. Open source projects are the main driver of this change, every popular open source projects gets a lot of drive by AI pull requests that waste maintainers’ time. Projects come up with their own way of blocking people (https://github.com/ghostty-org/ghostty/blob/main/.github/VOU...) but having this be a GitHub feature is a much easier option for most.
In New repository settings for configuring pull request access
Good questions. > why did it write so much to begin with? It's an incremental project covering a complex domain. At any time, the code has to stay balanced in a spot that addresses correctness and performance across things like pty parsing, a terminal grid, stateful pty behavior, rendering, scrollback history, font glyphs, and like all software there is a fractal of idiosyncrasies that sprout up. And that's just the terminal side. Unless you can see the future, like most software, so much of the project is trying things and seeing what happens at the periphery, like how to represent "row damage" and apply it in a way that works with macOS Core Graphics and 1000 other things. e.g. Can you tell me off the top of your head what the trade-offs are of representing the terminal contents/scrollback as a pre-wrapped grid vs. a list of logical lin
Read the rest
es that are soft-wrapped on the fly? Did you enumerate them all and correctly weigh them such that you can pick the ideal solution ahead of time? No. You just kinda make educated decisions and find out in practice what the exact weight of the trade-offs are. You should see the amount of iterations a human needs on these kinds of projects. https://github.com/ghostty-org/ghostty has almost 18,000 commits. So does https://github.com/gnachman/iterm2. So does https://github.com/kovidgoyal/kitty. > why do you assume that now there's no more debt? I don't. Like all software, you try to ratchet into better and better positions, and you try to come up with metrics that can tell you "You are here" with regard to rather fuzzy goals like "it should be correct and performant and nice to use". But I can look at individual findings and their solution to go "yes, this improves the code." And on principle I think that, e.g. correct/DRY/simple by-construction is superior to by-convention, and I assume it helps future agents reason about the system and make future edits, and it gives them singular places to make changes that impact multiple components just like it would a human. But how much did it actually matter?
In There's No Limit to How Bad Code Can Get
I've originally asked for it two weeks ago on the Ghostty github discussions page [1], and it turns out someone decided to just go ahead and develop it. It looks awesome. What's most stunning to me is that back in the 90s and 00s we would have waited several years to someone try and attempt something like this. Huge thanks to GH user mikewang817 [1] https://github.com/ghostty-org/ghostty/discussions/13291 P.S. I changed "agent" to "app" in the title since that makes much more sense. I think the author used the wrong word there. Maybe tformula was initially meant for only agents and then it turned out to work for all CLI apps and the title hasn't been updated yet.
In TFormula: Render LaTeX from any CLI app directly in Kitty-compatible terminals
> I have a fairly up to date Zig installed via Homebrew. This is likely the problem. Latest Zig is 0.16 and Ghostty (and therefor Ghostel) require exactly Zig 15.2. I just updated our code to have a better error message and make it clear that the problem is the Zig version. See https://github.com/dakra/ghostel/pull/541 jFYI, Ghostty issue to support 0.16 is here: https://github.com/ghostty-org/ghostty/issues/12228 So for your homebrew zig you probably have to: brew uninstall zig brew install zig@0.15
In Ghostel.el: Terminal emulator powered by libghostty

Showing the 15 most recent of 128 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.