TL;DR
Get business pricing on monitors, keyboards and dev gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
Mitchell Hashimoto announced libghostty-vt 1.0, marking the library and its C ABI stable under a formal compatibility policy. He says it is already used in products including JetBrains IDEs and OrbStack, and the release adds packaging and build materials intended to support distribution by operating-system and Linux package maintainers.
Libghostty-vt 1.0, the terminal-emulation library extracted from Ghostty, has been released with a stable C ABI and a formal compatibility policy, project creator Mitchell Hashimoto said. The milestone is intended to let software developers link to the library and package maintainers distribute it with greater confidence, as Hashimoto reports that it is already used in products ranging from JetBrains IDEs to OrbStack.
Hashimoto describes libghostty-vt as a portable, high-performance C library built from Ghostty’s terminal-emulation core. He said the C API has grown into a complete terminal emulator and that the library now runs in production across hundreds of products, both free and commercial. These adoption figures and examples come from the project creator’s report, not an independent usage audit.
The release’s main technical promise is ABI stability: applications should be able to link against compatible releases without unexpected binary incompatibilities. The API uses opaque handles and enum-based getters and setters, while checks in the project’s continuous-integration system compare changes against ABI baselines. Hashimoto said newer headers used with an older library return an unsupported result for unavailable features rather than causing a crash or undefined behavior.
Version 1.0 also comes with signed source tarballs, a separate dependencies tarball for offline builds, headers, shared and static libraries, pkg-config files and a CMake package configuration. The library is MIT-licensed, according to Hashimoto, and its runtime requires only libc; the source report says it can also be built freestanding. A machine-readable dependency manifest records versions, licenses and hashes for packaging review.
A stable C interface can make it practical for other applications to use the same terminal-emulation engine instead of maintaining separate implementations. That matters because terminal behavior is complicated: differences in handling text, resizing, graphics and other features can create bugs for users and developers. A common library does not by itself guarantee identical behavior or eliminate defects, but it gives adopters a shared implementation to build on.
The release may also lower the friction for Linux distributions and operating-system packagers. A defined ABI, standard installation files and offline build materials address practical concerns that arise when packaging software for users outside the original project. The reported use in JetBrains products and other tools suggests the library’s reach extends beyond Ghostty itself; the scale and breadth of that adoption remain based on the project’s own account.
Products Worth Considering
Logitech MX Mechanical Wireless Illuminated Keyboard, Tactile Quiet, Graphite
DJI Mini 3 Pro Fly More Vlogger Combo with DJI RC
Logitech MX Keys Combo for Business Keyboard and Mouse – Graphite
As an affiliate, we earn on qualifying purchases.
From Ghostty Core to Library
Ghostty is a terminal application whose core emulation code was made available as a separate library. Hashimoto wrote a little over a year before this release that libghostty was coming; at that point, he said, a Zig module had been merged, there was no C API and Ghostty was the only consumer. The 1.0 announcement describes a substantial change from that starting point: a C interface, external adopters and a policy for binary compatibility.
Hashimoto named JetBrains IDE terminals among the largest deployments, citing a JetBrains report of more than 12.5 million active users across products such as IntelliJ IDEA, PyCharm and GoLand. He also said Neovim maintainers had approved a proposed change to replace libvterm with libghostty-vt, but were waiting for a tagged release before merging it. Other examples in his report include KDE experimentation, Vercel’s Turborepo, devenv, Ghostel, ghostty-web and commercial products including OrbStack. The examples indicate varied interest, but they do not all represent completed or equivalent deployments.
“The 1.0 release means both the library itself and the C ABI are now stable.”
— Mitchell Hashimoto, Ghostty creator
Adoption and Compatibility Details
The announcement does not provide an independent audit of the claimed hundreds of products or a breakdown of how many use the library in production, experimentation or proposed integrations. The cited 12.5 million figure is attributed to a JetBrains report, but the source does not specify the report’s date or methodology. Neovim’s approved pull request is described as awaiting a release, so the announcement does not establish that the change has already shipped to users.
The ABI policy describes the project’s compatibility commitments, but the source does not detail how long each release branch will be supported or how quickly fixes will be issued. It also does not provide independent performance comparisons or a complete account of how each dependency is handled on every platform. Those questions will matter to teams evaluating the library for particular products.
Packaging and Downstream Releases
The immediate next step is for downstream projects and distribution maintainers to evaluate the 1.0 source and dependency tarballs and incorporate the library through their normal release processes. Hashimoto said the tagged version should allow Neovim’s maintainers to proceed with packaging considerations. That is a stated opportunity, not confirmation of a merge or release date.
Future adoption will show whether the ABI policy and packaging materials work for maintainers across supported systems. Developers considering libghostty-vt can review the project’s packaging documentation and compatibility policy, then check the status of the particular integration they rely on. The supplied announcement gives no schedule for later releases or a list of planned features.
Key Questions
What is libghostty-vt 1.0?
It is the 1.0 release of a C library for terminal emulation extracted from Ghostty. The project says the library and its C ABI are now stable.
What does a stable C ABI mean for developers?
An ABI defines how compiled programs interact with a library. The project’s compatibility policy is intended to let applications link against compatible library releases without unexpected binary changes; it does not mean every future version will have identical features.
Which products use libghostty?
Hashimoto reports use in JetBrains IDE terminals and products including Turborepo and OrbStack, among other projects. His report also distinguishes some experiments and proposed integrations from deployed uses.
Is the library available for distribution packaging?
The release includes source and dependency tarballs, build and installation files, and packaging documentation. Hashimoto says these materials are designed to support standard packaging, including offline builds.
Has Neovim switched to libghostty-vt?
Not based on the supplied report. Hashimoto says a pull request to replace libvterm had been approved, with maintainers waiting for a tagged release before merging so distributions could package the dependency separately.
Source: mitchellh.com
