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 an enforced ABI compatibility policy for the C library extracted from Ghostty. He says it is already used across products including JetBrains IDEs and Turborepo; the release also adds distribution-focused build and packaging support.
Mitchell Hashimoto has announced libghostty-vt 1.0, the first release that he says gives the terminal-emulation library and its C application binary interface (ABI) a stable compatibility policy. The release is intended to let software developers link against the library and package maintainers distribute it with greater confidence, as its use expands beyond the Ghostty terminal application.
Libghostty-vt is a portable C library for terminal emulation, extracted from Ghostty’s core. Hashimoto says the C API has developed into a complete terminal emulator and is now used in production by millions of people across hundreds of free and commercial products. Those reach figures are his account; the post does not provide an independent survey or a list covering every product.
Among the uses he identifies, JetBrains IDE terminals now run on the library. Hashimoto cites a JetBrains report of more than 12.5 million active users across products including IntelliJ IDEA, PyCharm and GoLand. Vercel’s Turborepo uses it to render task output in a terminal interface, while other named projects include devenv, Ghostel for Emacs, and ghostty-web, a WebAssembly build with an Xterm.js-compatible API.
The post also describes an approved Neovim pull request to replace libvterm with libghostty-vt, pending a tagged release so distributions can package the dependency separately. KDE developers are experimenting with a Konsole replacement using the library. Hashimoto says community bindings exist for multiple languages and that a community-maintained project list contains more than a hundred projects. These examples indicate adoption, but do not mean every proposed integration has shipped.
A Stable Base for Terminal Software
The 1.0 designation addresses a practical obstacle for software that wants to reuse terminal emulation instead of maintaining its own implementation: compatibility across library updates. Hashimoto says the release follows semantic versioning and introduces strict ABI promises, giving applications a defined basis for linking and distributions a clearer basis for packaging.
The design is intended to make changes less likely to break existing consumers. The API uses opaque handles and enum-keyed getters and setters; when newer headers request unsupported values from an older library, the API returns a GHOSTTY_UNSUPPORTED result, according to the post. Hashimoto also says non-opaque structures are sized or include reserved space so fields can be added later.
That matters to users indirectly: shared terminal infrastructure can appear inside IDEs, development tools and other applications, rather than only in a standalone terminal. But the announcement does not establish that adoption will continue, or that the library will suit every terminal project. Its immediate significance is that outside developers and distributors can now build around a stated compatibility policy.
Popular right now
Hisense 43-Inch E6 Cinema Series Hi-QLED 4K UHD Smart Fire TV (43E6QF)
TCL 43-Inch 4K UHD Smart LED Roku TV (43S435, 2021 Model)
Apple AirPods Pro 3 Wireless Earbuds with Active Noise Cancellation
As an affiliate, we earn on qualifying purchases.
Hashimoto writes that Ghostty began in 2022 and that, a little over a year before this release, libghostty was still at an earlier stage: its Zig module had been merged, but it had no C API and Ghostty was its only consumer. The 1.0 announcement marks a change from an internal component to a separately released library with external users.
The library has a release cycle separate from Ghostty. Its release tarballs contain the files and dependencies needed for libghostty-vt, rather than the full application. The build installs shared and static libraries, headers, pkg-config files and a CMake package configuration, and supports common installation options such as –prefix and DESTDIR.
Hashimoto says each release includes a signed source tarball and a companion dependencies tarball, allowing distributions to build offline. The library is MIT licensed, according to the post, and requires only libc at runtime, with a freestanding build also available. Its dependencies are listed in a machine-readable manifest with versions, SPDX licenses and hashes.
“The 1.0 release means both the library itself and the C ABI are now stable.”
— Mitchell Hashimoto, libghostty project lead
Adoption and Compatibility in Practice
The release post does not give an independent audit of the stated millions of users or hundreds of products. Its JetBrains figure is attributed to a report by the company, but the post does not specify the report’s date or define its active-user measurement window. The figure should not be read as a count of people using libghostty-vt across all products.
Some uses are at different stages. The Neovim change is described as an approved pull request awaiting a tagged release, and the KDE project as an experiment; neither description confirms a completed, generally available integration. The announcement also does not report independent long-term testing of ABI compatibility across all supported operating systems, or spell out a full support matrix and release schedule.
Packaging and Integrations Ahead
The tagged 1.0 release gives Neovim maintainers the release they said they needed before merging the approved replacement and allows distributions to package the library as a separate dependency. Packagers can use the accompanying source and dependencies tarballs, build documentation and licensing manifest to evaluate distribution through their standard tools.
Hashimoto says CI checks ABI changes against a committed baseline on Linux and golden type manifests on macOS and WebAssembly; on ELF platforms, exported symbols are versioned. Future releases will be the test of how that policy holds as the API changes and new consumers arrive. The announcement does not specify dates for the Neovim merge, KDE experiment or further adoption milestones.
Key Questions
What is libghostty-vt 1.0?
It is version 1.0 of a C terminal-emulation library extracted from Ghostty. Project lead Mitchell Hashimoto says the release establishes a stable library and C ABI under semantic versioning.
What does a stable C ABI mean for developers?
An ABI defines how compiled programs interact with a library. Hashimoto says libghostty-vt’s policy is intended to let applications link against it and let distributors package it while maintaining compatibility across releases.
Which products are already using it?
Hashimoto identifies JetBrains IDE terminals, Vercel’s Turborepo, devenv, Ghostel and ghostty-web, among others. He also describes a Neovim pull request awaiting a tagged release and an experimental KDE effort, so those should not be treated as completed deployments.
Is libghostty-vt open source, and what does it require?
Hashimoto says the library is MIT licensed. At runtime, he says it needs no more than libc, and it can also be built freestanding; its release materials include dependency and licensing information for packagers.
Does 1.0 mean every integration is stable or complete?
No. The 1.0 claim concerns the library’s release and ABI policy. The announcement describes some integrations as experiments or pending a tagged release, and it does not establish that every listed project is complete or that all uses have been independently verified.
Source: mitchellh.com
