TL;DR
Get the latest gadgets delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
Mitchell Hashimoto announced libghostty-vt 1.0, marking stable API and ABI commitments for the portable C terminal-emulation library extracted from Ghostty. He says it is already used in products including JetBrains IDE terminals and Vercel’s Turborepo; the release also adds packaging materials for operating systems and Linux distributions.
Mitchell Hashimoto has released libghostty-vt 1.0, the first stable release of the portable C terminal-emulation library extracted from Ghostty. The milestone sets stable API and ABI commitments and adds packaging tools for distributions and developers, making it easier to use the terminal engine independently of the Ghostty application.
Hashimoto describes libghostty-vt as a high-performance C library for terminal emulation. He says its C API has grown into a complete terminal emulator and is now used in production across free and commercial products. The library has a release cycle separate from Ghostty itself, so projects can consume and package it as an independent dependency.
The 1.0 designation means the library follows semantic versioning and strict ABI compatibility promises, according to Hashimoto. Its design uses opaque handles and enum-based accessors for many values, which he says can allow additions without introducing new exported symbols. Compatibility checks run in continuous integration against recorded baselines on Linux, macOS and WebAssembly; exported symbols are versioned on ELF systems.
The release also supplies signed source and dependency tarballs, documentation, licensing information and build support for standard installation paths and package tools. Hashimoto says the dependency tarball allows distributions to build offline. The library is MIT licensed and, according to his report, needs only libc at runtime; it can also be built freestanding. Its listed dependencies are permissively licensed.
A stable ABI can reduce the cost and risk of adopting a common terminal engine. Developers can link programs against the library, while distribution maintainers can package it with a clearer expectation that compatible updates will not break consumers. That matters for terminal emulators and other software that renders command-line interfaces, including developer tools.
Hashimoto says more people use terminals powered by libghostty than use the Ghostty application, though his report does not provide a measurement method or a precise count for that comparison. His examples indicate adoption beyond standalone terminal apps, including IDEs and tools that display interactive task output. The release makes that ecosystem easier to depend on through a separately versioned library and established packaging materials.
The impact will depend on continued compatibility and adoption by downstream projects. A 1.0 release is a commitment about the project’s interface and release policy, not proof that every potential consumer has migrated or that future maintenance is guaranteed.
Popular right now
TCL 75-Inch QM6K QLED Mini LED 4K HDR Smart Google TV, 144Hz
iRobot Roomba Plus 678 Robot Vacuum and Mop with AutoWash Dock
Dyson R3 Nurovi Spot+Scrub UV Robot Vacuum
As an affiliate, we earn on qualifying purchases.
From Ghostty Core to Independent Library
Hashimoto says the library began as part of the Ghostty project, started in 2022. In an earlier post, he described libghostty as forthcoming: the Zig module had been merged, but a C API did not yet exist and Ghostty was its only consumer. The 1.0 announcement marks a change from that early stage to a separately released C library with an ABI policy.
Hashimoto points to several existing or prospective uses. He says JetBrains IDE terminals now run on libghostty, citing a JetBrains report of more than 12.5 million active users across products. He also reports an approved Neovim pull request to replace libvterm, pending a tagged release so distributions can package the dependency. Other named examples include Turborepo, devenv, Ghostel, ghostty-web and OrbStack; KDE developers are described as experimenting with a Konsole replacement.
Those examples have different statuses: some are reported as current integrations, while others are experiments or proposals. Hashimoto also points to community language bindings and a list tracking more than a hundred projects, but the source does not independently verify their activity or the scale of use.
““The 1.0 release means both the library itself and the C ABI are now stable.””
— Mitchell Hashimoto, libghostty creator
Adoption Claims and Compatibility in Practice
The announcement does not provide an independently audited user total, adoption database or methodology for the claim that libghostty-powered terminals reach more people than Ghostty itself. The JetBrains figure is attributed to a company report, and the source does not specify its measurement date or define “active users.”
It is also unclear from the report which projects have completed releases using version 1.0, rather than integrating an earlier revision, proposing a change or testing the library. Neovim’s change is described as an approved pull request awaiting the tagged release, while KDE’s work is described as experimentation.
The ABI policy and automated checks are documented by the project, but their long-term record will become clearer as consumers package releases and the library evolves. The source does not detail a support period, security-response policy or guarantees beyond ABI compatibility.
Downstream Packaging and Integrations
The immediate next step is for distributions and downstream projects to evaluate the tagged 1.0 release, build from its source and dependency tarballs, and package the library through their standard processes. Hashimoto says the release should allow Neovim maintainers to proceed with the approved change once the separately packaged dependency is available.
Further adoption will depend on projects completing integrations and maintaining them against future releases. The published packaging guide and ABI checks provide a basis for that work; the source material does not announce a specific next release date or a schedule for additional integrations.
Key Questions
What is libghostty-vt 1.0?
It is the first stable release of libghostty-vt, a portable C terminal-emulation library extracted from Ghostty. Its 1.0 status brings a stable API and ABI policy, according to creator Mitchell Hashimoto.
What does ABI stability mean for developers?
ABI stability is a promise about compatibility at the binary level, which can let programs dynamically link to a library across compatible updates. Hashimoto says libghostty-vt uses compatibility checks and versioned symbols on ELF systems to enforce its policy.
Which products are reported to use the library?
Hashimoto names JetBrains IDE terminals, Vercel’s Turborepo, devenv, Ghostel, ghostty-web and OrbStack, among other projects. The reported projects vary in status; some are integrations, while KDE work is described as experimental and Neovim’s change as an approved pull request awaiting the release.
What is included for Linux distributions and other packagers?
The release includes signed source and dependency tarballs, headers, shared and static libraries, pkg-config files, a CMake package configuration and packaging documentation. Hashimoto says the dependency tarball supports offline builds.
Is libghostty-vt free of runtime dependencies?
Hashimoto says it needs only libc at runtime and can be built freestanding. The library is MIT licensed and uses several permissively licensed dependencies at build time, according to the report.
Source: mitchellh.com
