TL;DR
Get business pricing on networking and server gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
Mitchell Hashimoto has announced libghostty-vt 1.0, establishing semantic versioning and an enforced ABI stability policy for the portable terminal-emulation library. He reports adoption in JetBrains IDEs and a range of other products, with the release also adding packaging materials for operating systems and distributions.
Mitchell Hashimoto has announced libghostty-vt 1.0, the first stable release of the portable C library for terminal emulation extracted from Ghostty. The release formalizes semantic versioning and C ABI compatibility commitments, a change intended to give software developers and operating-system distributors a dependable basis for linking, packaging and updating the library.
Hashimoto describes the C API as a complete terminal emulator that is already used in production. He says it powers the terminals in JetBrains IDEs, including IntelliJ IDEA, PyCharm and GoLand, and cites a JetBrains report putting their combined reach at more than 12.5 million active users. That figure is attributed to JetBrains through Hashimoto’s report; it is not an independently established user count for the library itself.
Other projects named by Hashimoto include Vercel’s Turborepo, which uses the library to render task output in its terminal interface, and OrbStack, which embeds it in a commercial product. He also points to work in Neovim, KDE’s Konsole, Ghostel for Emacs and a WebAssembly build with an Xterm.js-compatible API. The Neovim change, he says, has an approved pull request but was waiting for a tagged release so distributions could package the dependency separately.
The release includes more than the compatibility commitment. Its materials include signed source and dependency tarballs, installation support for shared and static libraries, headers, pkg-config files and a CMake package configuration. The project says distributions can build from the dependency tarball offline. Hashimoto says the library is MIT licensed, needs only libc at runtime, and has no copyleft code in its dependency tree.
A Stable Base for Terminal Software
A stable C ABI lets applications and distributions rely on a library across updates without rebuilding every dependent program for each change. For terminal software, that could reduce the need for each editor, development environment or command-line interface to maintain its own emulator implementation. The 1.0 policy makes that prospect more practical by spelling out how compatibility is maintained and checked.
The reported adoption also shows that the library’s reach extends beyond Ghostty, the terminal application from which it was extracted. If the reported deployments and community projects continue to grow, improvements to a shared terminal engine could benefit multiple products. That is a possible consequence of shared infrastructure, not a guarantee that every project will adopt it or that users will see identical features across those products.
Packaging support matters for a different reason: a stable API is less useful if distributions cannot build or ship it using their normal processes. Hashimoto says the release supplies conventional installation files, dependency licensing information and offline build inputs, addressing practical requirements for both open-source and commercial consumers.
Products Worth Considering
Logitech MX Mechanical Wireless Illuminated Keyboard, Tactile Quiet, Graphite
Samsung Odyssey G7 40-Inch WUHD Curved Gaming Monitor (G75F)
Anker SOLIX C1000 Gen 2 Portable Power Station, 1,024Wh
As an affiliate, we earn on qualifying purchases.
Ghostty began in 2022, according to Hashimoto. In an earlier post, a little over a year before this release report, he described libghostty as an effort whose Zig module had been merged but whose C API did not yet exist; at that point, Ghostty was its only consumer. The 1.0 announcement marks a shift from that early state to an independently released C library with its own release cycle.
Hashimoto says ABI compatibility is enforced in continuous integration. The checks compare changes against a committed baseline on Linux and golden type manifests on macOS and WebAssembly; on ELF platforms, exported symbols are versioned. The API uses opaque handles and enum-keyed accessors, among other design choices intended to let the library add functionality while preserving compatibility. These are project-reported engineering measures, not an independent audit of the implementation.
The library is written around Ghostty’s terminal-emulation core, but has its own tarballs containing the files and dependencies needed to build it. Hashimoto lists permissively licensed dependencies for SIMD processing, Unicode grapheme data and Kitty graphics image decoding. He says a freestanding build is possible without libc, although the regular runtime requirement is libc.
““The 1.0 release means both the library itself and the C ABI are now stable.””
— Mitchell Hashimoto, Ghostty creator and author of the release report
Adoption and Compatibility Details
The release report does not provide a full, independently verified inventory of products using libghostty-vt, nor does it specify what share of the cited JetBrains user base runs the library at a given time. The 12.5 million figure is attributed to a JetBrains report and refers to active users of the named IDE products, not a measured count of people using libghostty across all projects.
It is also not clear from the report which Neovim release will incorporate the approved change, when that release might ship, or how quickly distributions will package libghostty-vt 1.0. Hashimoto describes the ABI policy and its automated checks, but the source material does not include an external review or a long-term record of compatibility across future releases. Adoption by projects experimenting with the library should not be treated as a commitment to ship it.
Packaging and Project Integration
The immediate next step for consumers is to build or package the 1.0 release using its source and dependency tarballs, installation files and documentation. Hashimoto says the release is intended to let distributions package libghostty-vt through standard tooling; actual availability will depend on individual maintainers and release schedules.
For Neovim, Hashimoto says the tagged release should meet the condition maintainers set before merging the approved pull request. The report does not announce a merge date. Other projects may continue evaluating the library, but no future integrations or delivery dates are confirmed in the source material. The key milestone now is whether the stable ABI and packaging support translate into routine use across downstream software and distributions.
Key Questions
What is libghostty-vt 1.0?
It is the stable release of a portable C library for terminal emulation, extracted from Ghostty. The release establishes semantic versioning and an ABI compatibility policy.
What does a stable C ABI mean for developers?
An ABI, or application binary interface, sets rules for how compiled programs interact with a library. Hashimoto says libghostty-vt 1.0 commits to compatibility across releases, helping developers link applications and distributions package updates with greater confidence.
Which products already use the library?
Hashimoto reports use in the terminals for JetBrains IDEs and in projects including Vercel’s Turborepo and OrbStack. He also describes work involving Neovim, KDE’s Konsole, Ghostel and a WebAssembly build; those examples have different adoption statuses.
Does the 1.0 release mean Neovim has switched to libghostty?
Not yet, based on the release report. Hashimoto says an approved pull request was waiting for a tagged release so distributions could package the dependency separately; the report does not confirm that the change has been merged or shipped.
What license and dependencies does libghostty-vt have?
Hashimoto says the library is MIT licensed, has libc as its normal runtime requirement and uses permissively licensed dependencies. He says the dependency tree contains no copyleft code and that the release includes a machine-readable dependency and licensing manifest.
Source: mitchellh.com
