Libghostty 1.0 Freezes a C ABI Under Terminals Used by JetBrains' 12.5 Million Users
Software / news
Libghostty 1.0 Freezes a C ABI Under Terminals Used by JetBrains' 12.5 Million Users
Mitchell Hashimoto's Nov. 6 release promises semantic versioning and symbol-level compatibility, 10 days after the Ghostty 1.4 notes said no such tag existed.

Mitchell Hashimoto released libghostty-vt 1.0 on Nov. 6, declaring both the terminal-emulation library and its C ABI stable. In his announcement, he lists JetBrains IDE terminals, which the post says reach more than 12.5 million active users, among the embedders.
The timing is the story. Ghostty 1.4.0, dated Oct. 27, said the API "is still marked as a work in progress and broke compatibility several times during this cycle," and warned to "expect more breaking changes before a tagged release." The tag arrived 10 days later, ahead of the "before Ghostty 1.5" promise in those notes. Ghostty 1.5 is planned for March 2027.

What 1.0 promises to people who link against it
The release commits to semantic versioning with strict ABI compatibility, which matters to Linux packagers who link the library dynamically. Objects are opaque handles, read and written through enum-keyed getters and setters so new values need no new symbols. A program built against newer headers and run against an older library gets GHOSTTY_UNSUPPORTED back instead of a crash.
Non-opaque structs carry their size or reserved padding so fields can be appended. CI checks ABI changes with libabigail, and ELF symbols are versioned. The library gets its own release cycle, separate from the Ghostty app, with signed source tarballs and an offline dependencies tarball.
The licence is MIT, and the post says the dependency tree holds no copyleft code. Its dependencies are simdutf and Google Highway for SIMD, a Unicode table, and Wuffs for decoding Kitty graphics protocol images.
Where it is tested and where it is only built
The post splits platforms into tested in CI and merely built. Anyone shipping to the second group is on their own for runtime bugs.
| Status | Targets |
|---|---|
| Built and tested | Linux (glibc, musl) on x86_64 and aarch64; macOS 13+; iOS 13+; FreeBSD; Windows x86_64; Android; WebAssembly (wasm32, freestanding) |
| Built, not tested | Bare metal (riscv32, thumb), WASI, Windows arm64, illumos x86_64, 32-bit x86 |
The Windows row is the practical one. The Ghostty 1.4 notes dropped the roadmap for a Windows Ghostty GUI and told downstream projects to use libghostty there. It's FOSS's coverage by Sourav Rudra repeats that, and says libghostty and libghostty-vt "are already built for Windows."
Who is already using it
The 1.4 notes claim adoption by "dozens of free and commercial terminal emulators used by millions of people" without naming any. The 1.0 post does name them: JetBrains, a Neovim pull request replacing libvterm that is approved and waiting on a tagged release, an experimental Konsole replacement from KDE called kwi, Vercel's Turborepo, devenv, Antithesis, the Emacs package Ghostel, ghostty-web, OrbStack, and the agent tools herdr and cmux. Bindings exist for Rust, Go, JavaScript, Swift, Python, .NET, Elixir, Dart and Java.
Anyone who pinned a commit after the 1.4 warning now has a version number to move to. Neovim's libvterm replacement is waiting on a tagged release, so its merge is the first adopter signal to watch.
The agent tools on that list sit in the same territory as Stroq, which audits Claude Code and Cursor sessions, and another young open-source project with firm views on contributions is Rune.
Sources
More in Software
- 01Levien's Next-100 Rust GUIs Post Counts About 20 New Toolkits and Bets Against egui's Immediate ModeThe Linebender author credits AI rewrites for the surge; egui's own README concedes the trade-off he is pressing on.
- 02C++26 Is Reopened: The 13–9–12 Ballot, the Enforced Label That Answers It, and What Is Still OpenSutter's Búzios report says the committee kept contracts, added one paper, and will send C++26 to a second ballot with no published date.
- 03OpenAI Says Codex Cannot Run in Docker for iOS Builds, and Docker Launches It With Codex's Sandbox OffBolin's November 18 post lists Seatbelt, Bubblewrap and MXC as Codex's three sandboxes; Docker's page defaults to --dangerously-bypass-approvals-and-sandbox.
- 04CLI-Anything Has 62,119 Stars and a README With Three Different Test TotalsThe HKUDS project turns desktop software into agent-callable CLIs; its own per-harness lines sum to 158 more tests than it reports.