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, establishing semantic-versioning and ABI compatibility commitments for the portable C terminal-emulation library. He says it is already used by products including JetBrains IDE terminals and Vercel’s Turborepo, while the release adds standard packaging materials for operating systems and distributions.
Libghostty-vt 1.0, the portable C terminal-emulation library extracted from Ghostty, has been released with a stable C ABI and tools intended to make it easier for operating-system distributions to package. Project creator Mitchell Hashimoto says the library is now used in products ranging from JetBrains IDEs to developer tools, extending Ghostty’s terminal technology beyond its own application.
Hashimoto describes 1.0 as a commitment to semantic versioning and strict ABI compatibility. The guarantees are intended to let distributors package the library and let applications dynamically link to it without routine library updates breaking compatibility. The C API, he says, has grown into a complete terminal emulator.
The release includes signed source and dependency tarballs, documentation, licensing manifests, headers, shared and static libraries, pkg-config files, and a CMake package configuration. The dependency archive follows Zig’s cache layout, allowing distributions to build the library offline. The build supports common installation controls, including –prefix and DESTDIR.
Hashimoto says the library is MIT licensed and needs only libc at runtime, with a freestanding build also possible. Its compile-time dependencies include simdutf, Google Highway, Unicode grapheme data and Wuffs for image decoding used by the Kitty graphics protocol. The report says those dependencies are permissively licensed and that the project provides a machine-readable manifest with versions, SPDX license identifiers and hashes.
The release gives software makers and distributors a stable C interface to reuse rather than implementing terminal emulation independently. For users, that could mean terminal behavior shared across editors, IDEs and command-line interfaces; for maintainers, a formal ABI policy and standard packaging files provide a clearer basis for updates and long-term support.
The reported reach is already broader than Ghostty as a standalone app. Hashimoto says JetBrains IDE terminals now use libghostty and cites a JetBrains report of more than 12.5 million active users. That figure refers to the IDE user base, not a separately measured count of people who actively use the terminal feature. The adoption examples indicate potential scale, but the report does not independently verify every deployment or quantify usage across all listed projects.
Products Worth Considering
Logitech MX Mechanical Wireless Illuminated Keyboard, Tactile Quiet, Graphite
Logitech MX Keys Combo for Business Keyboard and Mouse – Graphite
LG UltraGear 32GX850A-B 32-inch 4K UHD Glossy OLED Gaming Monitor
As an affiliate, we earn on qualifying purchases.
From Ghostty Core to C Library
Ghostty is a terminal application whose core emulation technology was separated into libghostty for reuse by other software. Hashimoto says that a little over a year before the 1.0 announcement, the project had a Zig module but no C API, and Ghostty was its only consumer. The 1.0 release marks a change from that early stage to an independently packaged library with an ABI policy.
Among the examples Hashimoto lists, Neovim has an approved pull request to replace libvterm with libghostty-vt; its maintainers were waiting for a tagged release before merging so distributions could package the dependency. He also points to KDE experimentation, Vercel’s Turborepo, devenv, Emacs-related projects, a WebAssembly build, and commercial products such as OrbStack. These are at different stages: the report does not describe all of them as completed production deployments.
“The 1.0 release means both the library itself and the C ABI are now stable.”
— Mitchell Hashimoto, libghostty creator
Adoption and Compatibility Details
The report does not give a release date, a full list of platforms tested, or independent measurements of how many people use libghostty-powered terminals. The 12.5 million figure is attributed to a JetBrains report about active users of its IDEs, and does not establish how many use the terminal within those products. It is also not clear from the report which listed projects have shipped integrations and which remain experimental or proposed.
The release sets out the project’s ABI policy, but the report does not detail how future compatibility disputes or exceptional breaking changes would be handled. Nor does it provide performance comparisons against other terminal-emulation libraries. Those questions are separate from the stated 1.0 guarantees and should not be inferred from the adoption examples.
Distribution Builds and Integrations
The immediate next step for distributors is to evaluate the release tarballs, dependency manifest and packaging documentation and decide whether to include libghostty-vt in their official packages. Neovim’s maintainers can also assess the tagged release against the dependency requirement described in Hashimoto’s report.
Further uptake will depend on project maintainers integrating the library and on packaged versions being available across operating systems. Hashimoto says libghostty has its own release cycle, separate from the Ghostty application; the report does not announce a timetable for later releases or promise a date for any particular integration.
Key Questions
What is libghostty-vt 1.0?
It is the 1.0 release of a portable C library for terminal emulation, extracted from Ghostty’s core. The release establishes the project’s stated stable ABI and semantic-versioning commitments.
What does the stable ABI mean for developers?
The project says applications can dynamically link to the library with stronger expectations that compatible releases will not break their binary interface. Hashimoto says its design uses opaque handles and versioned symbols on ELF platforms, with compatibility checks in continuous integration.
Which products use the library?
Hashimoto names JetBrains IDE terminals, Vercel’s Turborepo, devenv, OrbStack and other projects. The report also describes a proposed Neovim change and KDE experimentation, so not every example represents a completed production integration.
Is the library free of runtime dependencies?
Hashimoto says it requires only libc at runtime, and can be built freestanding. It has compile-time dependencies, which the project lists in a machine-readable manifest.
What happens after the 1.0 release?
Distributions can evaluate the packaging materials, while application maintainers can test or ship integrations against the tagged release. The announcement does not specify dates for future releases or for projects that have not yet adopted the library.
Source: mitchellh.com
