Ghostty terminal emulator; its repo also ships libghostty-vt, the embeddable terminal-emulation library that reached 1.0 on November 6, 2026.
Mitchell Hashimoto released libghostty 1.0 on November 6, the first stable version of the terminal-emulation engine extracted from his Ghostty terminal app. In his release post he describes it as a "portable, high-performance C library for terminal emulation," and says the 1.0 label means "the library itself and the C ABI are now stable." The post was the top story on Hacker News on Saturday, with more than 600 points.
Why it matters: almost every developer tool that shows a shell, from IDEs and editors to build-tool dashboards and AI coding agents, ends up writing or bundling its own terminal emulator and fixing the same escape-sequence edge cases. RuntimeWire frames the release as a chance to stop duplicating that work. A frozen ABI is the piece that was missing: Linux distributions can ship one shared copy, and apps can upgrade the library without recompiling.
What "1.0" actually promises
The library is formally libghostty-vt. According to Hashimoto's post:
- Semantic versioning with strict ABI rules. Objects are opaque handles, and values are read and written through a small set of enum-keyed getters and setters, so new fields don't need new symbols.
- Forward compatibility. If an app built against newer headers runs on an older library, unsupported calls return
GHOSTTY_UNSUPPORTEDrather than crashing. Structs carry their own size and enums are pinned toint. - ABI checked in CI. Linux builds are compared against a committed baseline with libabigail; macOS and WebAssembly are checked against golden type manifests. ELF builds use versioned symbols.
- Packaging basics. Each release has a signed source tarball, a dependencies tarball for offline builds, a SONAME, pkg-config and CMake files, and a packaging guide in the Ghostty repo.
- Small footprint. It needs only libc at runtime by default, creates no threads, and allocates only through a caller-supplied allocator. The post says the WebAssembly build is under a megabyte with everything on.
The post says the code is MIT-licensed and that there is no copyleft code anywhere in its dependency tree (simdutf, Google Highway, a Unicode table and Wuffs for Kitty graphics images).
Where it runs
| Status | Platforms (per the release post) |
|---|---|
| Built and tested in CI | Linux (glibc and musl, x86_64/aarch64), macOS 13+, iOS 13+, FreeBSD, Windows x86_64, Android (aarch64, x86_64, arm), WebAssembly |
| Built but not tested | Bare metal (riscv32, thumb), WASI, Windows arm64, illumos, 32-bit x86 |
Who already uses it
Hashimoto lists real adopters, which is what makes this more than a library announcement:
- JetBrains: the terminal in IntelliJ, PyCharm, GoLand and its other IDEs now runs on libghostty. The post cites JetBrains' figure of more than 12.5 million active users.
- Neovim: an approved pull request swaps libvterm for libghostty-vt and was waiting on a tagged release, which 1.0 now provides.
- Others: an experimental Konsole replacement at KDE, Vercel's Turborepo TUI, devenv, OrbStack, a web build with an Xterm.js-compatible API, and an Emacs package. The post also says testing firm Antithesis used the library to fuzz terminal apps and found bugs in btop and others.
Community bindings exist for Rust, Go, JavaScript, Swift, Python, .NET, Elixir, Dart and Java, and the post says a community list tracks well over a hundred projects. Its sample "ghostling" terminal is about 1,500 lines of C.
One performance claim stands out but comes only from the author: 10,000 live terminals running shells on a 4-core, 8 GB Linux server (using dash, because bash used too much memory). Treat it as an upper bound from a favourable setup.
The caveats people raised
According to TLDR's round-up of Hacker News and Lobsters discussion, reaction was strongly positive, with three recurring questions: how it compares to GTK-bound libvte, whether the getter/setter design will leak implementation details over time, and whether building from source with Zig, a language still before 1.0, will make life harder for distro packagers. The post doesn't spell out a roadmap beyond implementing more terminal protocols and keeping things stable.
Who should care
- Tool builders who embed a terminal (IDE plugins, agent harnesses, TUIs in the browser) now have a stable, permissively licensed engine to link against instead of maintaining their own parser.
- Neovim users: the approved libvterm swap was waiting on a tagged libghostty release; watch the Neovim repo for when it merges and ships.
- Distro maintainers can start packaging it as a shared library; the docs and downloads are linked from the release post.
Sources
- Mitchell Hashimoto — Libghostty 1.0 mitchellh.com
- RuntimeWire — Libghostty 1.0 gives developers a stable terminal engine to embed runtimewire.com
- TLDR — Libghostty 1.0 tldr.tech
- Hacker News — front page ("Libghostty 1.0") news.ycombinator.com