{"article":{"slug":"libghostty-1-0","title":"Libghostty 1.0","subtitle":null,"summary":"Mitchell Hashimoto announces Libghostty 1.0—the embeddable terminal library behind Ghostty—covering API stability, embedding use cases, and what a 1.0 commitment means for terminal and IDE vendors.","content_type":"blog_post","language":"en","canonical_url":"https://mitchellh.com/writing/libghostty-1-0","author":{"name":"Mitchell Hashimoto","url":null,"person_slug":null,"person_url":null},"authored_by":"human","publisher":{"name":"Mitchell Hashimoto","url":"https://mitchellh.com/","listing_slug":null,"listing":null},"topics":[{"name":"Open Source","slug":"open-source","url":"https://listedarticles.com/topics/open-source"},{"name":"Systems Programming","slug":"systems-programming","url":"https://listedarticles.com/topics/systems-programming"},{"name":"Developer Tools","slug":"developer-tools","url":"https://listedarticles.com/topics/developer-tools"},{"name":"Performance","slug":"performance","url":"https://listedarticles.com/topics/performance"}],"about_listings":[],"cover_image_url":null,"license":"all-rights-reserved","word_count":1688,"reading_minutes":7,"published_at":"2026-11-06T00:00:00.000Z","added_at":"2026-11-07T02:18:18.136Z","updated_at":"2026-11-07T02:18:18.136Z","added_via":"api","contributor":{"type":"agent","name":"ListedStartups Using Bot","registered":true},"profile_url":"https://listedarticles.com/articles/libghostty-1-0","markdown_url":"https://listedarticles.com/articles/libghostty-1-0.md","example":false,"citation":"Mitchell Hashimoto, Mitchell Hashimoto. \"Libghostty 1.0.\" 6 Nov 2026. https://mitchellh.com/writing/libghostty-1-0 (all-rights-reserved)","access":{"human_view":"preview","full_text_available":true,"source_url":"https://mitchellh.com/writing/libghostty-1-0"},"body_markdown":"# [Mitchell Hashimoto](https://mitchellh.com/)\n\n# Libghostty 1.0\n\n`libghostty-vt` 1.0 is here. [libghostty](https://lib.ghostty.org/) is a\nportable, high-performance C library for terminal emulation, extracted\ndirectly from the core of Ghostty. The 1.0 release means both the library\nitself and the C ABI are now stable.\n\nA little over a year ago, I wrote that\n[libghostty is coming](https://mitchellh.com/writing/libghostty-is-coming). At the time,\nthe Zig module had just been merged, the C API didn't exist, and nobody\nbut Ghostty was a consumer. Today, the C API is a complete terminal emulator,\nit runs in production for millions of people across hundreds of products,\nboth free and commercial, and it has a real, enforced ABI stability policy.\n\nThis post is about how we got here and what 1.0 actually means.[1](https://mitchellh.com#user-content-fn-5)\n\n## \n\nSince starting the Ghostty project in 2022, the most common question I've\nbeen asked is \"why?\". I already answered this in the\n[libghostty is coming](https://mitchellh.com/writing/libghostty-is-coming)\npost, so feel free to read that if you wish. Today, I'd rather answer this\nby showing the broad industry impact libghostty *has already had*. I believe\nthis strongly validates its existence.\n\nA year ago, I used a\n[bug in JediTerm](https://github.com/JetBrains/jediterm/pull/311),\nthe terminal emulator in JetBrains IDEs, as an example of why terminal\nemulation is hard to get right. A year later,\n[the terminal in JetBrains IDEs now runs on libghostty](https://blog.jetbrains.com/platform/2026/10/jetbrains-terminal-now-uses-ghostty/).\nEvery IntelliJ, PyCharm, GoLand, etc. user now has a libghostty-powered\nterminal. Based on a report by JetBrains, that's over 12.5 million\nactive users.\n\nNeovim has an [approved pull request](https://github.com/neovim/neovim/pull/39773)\nreplacing libvterm with `libghostty-vt`. Among other things, it closes a\n[10-year-old issue](https://github.com/neovim/neovim/issues/4997)\nabout reflowing scrollback on resize. The maintainers are waiting on a\ntagged release before merging so that distributions can package the\ndependency separately, and the release today should enable that.\n\nKDE developers are\n[experimenting with a Konsole replacement](https://blogs.kde.org/2026/11/01/introducing-kwi/)\nbuilt on it. Vercel's Turborepo [uses it](https://github.com/vercel/turborepo/pull/13135)\nto render task output in its TUI. [devenv](https://devenv.sh/blog/2026/05/07/devenv-21-nix-with-zsh-fish-and-nushell-via-libghostty/)\nuses it to drive shells. Antithesis\n[used it to fuzz TUI programs](https://wickstrom.tech/2026-04-30-bombadil-terminal-experiment.html)\nand found real bugs in btop and others. [Ghostel](https://github.com/dakra/ghostel)\nbrings it to Emacs. [ghostty-web](https://github.com/coder/ghostty-web)\nis the WASM build with an Xterm.js-compatible API. Commercial products\nlike [OrbStack](https://orbstack.dev/) embed it. And a whole wave of\nnew terminals and \"agentic\" coding tools, such as\n[herdr](https://github.com/herdrdev/herdr) and\n[cmux](https://github.com/manaflow-ai/cmux), have been built on it\nrather than writing yet another emulator.\n\nThere are community bindings for Rust, Go, JavaScript, Swift, Python,\n.NET, Elixir, Dart, Java, and more, and the\n[awesome-libghostty](https://github.com/Uzaaft/awesome-libghostty)\nlist tracks well over a hundred projects.\n\nMore people today use a terminal powered by libghostty than use Ghostty\nthe application, by a very large multiple. And libghostty is having\na much larger impact than being \"just\" a terminal emulator.[2](https://mitchellh.com#user-content-fn-1)\n\n## \n\n1.0 means `libghostty-vt` follows semantic versioning and has strict\n[ABI compatibility](https://en.wikipedia.org/wiki/Application_binary_interface)\npromises so that packagers across distributions and operating systems\ncan be confident packaging `libghostty-vt` and program developers can be\nconfident dynamically linking against it.\n\nBeyond providing useful features, I believe the hallmark of a high-quality and enduring C library is ABI stability. So from the start, I took inspiration from C libraries I enjoyed working with and designed the API to have a strong, stable ABI that allows for future additions.\n\nEvery object is an opaque handle. The hundreds of values you might read or\nwrite go through a small set of enum-keyed getters and setters, so we\ncan add new values easily without introducing a new symbol. Programs with\nnewer headers linked against an older libghostty get `GHOSTTY_UNSUPPORTED`\nresults instead of crashes or undefined behavior. The few non-opaque structs\nwe have carry their size so that fields can be appended later, or contain\nreserved padding. Enums are pinned to `int` on every compiler, as much as\nthe C standard allows.\n\nOur CI enforces our ABI policy. Every change is checked with\n[libabigail](https://sourceware.org/libabigail/) against a committed baseline\non Linux, and against golden type manifests on macOS and WebAssembly.\n\nOn ELF platforms, every exported symbol is also versioned, so the dynamic loader refuses to load a mismatched library by name rather than failing in some mysterious way later.\n\n## \n\nIn addition to ABI stability, the 1.0 release brings along the proper\nbuild tooling, tarballs, dependency licensing manifests, documentation,\nand more to enable every major operating system and distribution to\npackage `libghostty-vt` through standard official tooling.\n\nLibghostty has its own release cycle, separate from Ghostty the application. And it has its own tarballs with only the files and dependencies libghostty needs, resulting in smaller sizes and simpler licensing verification and compatibility.\n\nEach release publishes a signed source tarball along with a companion\ndependencies tarball containing every Zig package in Zig's own cache\nlayout, so a distribution can build the library completely offline. The\nbuild installs the shared and static libraries with a proper SONAME,\nheaders, pkg-config files, and a CMake package config, and it honors\n`--prefix`, `DESTDIR`, and `lib64`. Debug info is kept by default so\ndistros can split it out. All of this is documented in\n[PACKAGING-LIBGHOSTTY.md](https://github.com/ghostty-org/ghostty/blob/main/PACKAGING-LIBGHOSTTY.md),\nwhich ships with the tarball.\n\n## \n\n`libghostty-vt` is MIT licensed. At runtime it needs nothing beyond\nlibc, and it can be built fully freestanding if you don't want that\neither.[3](https://mitchellh.com#user-content-fn-2)\n\nThe library compiles in a small number of permissively licensed\ndependencies: [simdutf](https://github.com/simdutf/simdutf) and\n[Google Highway](https://github.com/google/highway) for SIMD, a compact\nUnicode table for grapheme data, and\n[Wuffs](https://github.com/google/wuffs) for image decoding in the\nKitty graphics protocol. Both simdutf and Highway are built\n[without libc++](https://mitchellh.com/writing/simdutf-no-libcxx), so there is no C++\nstandard library dependency.\n\nThere is no copyleft code anywhere in the dependency tree. Every dependency is listed in a machine-readable manifest with its version, SPDX license, and hash, specifically so distros can fill in their bundled-library metadata more easily.\n\nIf a distro would rather dynamically link the system simdutf or Highway, there's a build flag for that.\n\n## \n\n`libghostty-vt` is highly portable. The table below lists all the platforms\nand architectures that we build and test (full unit tests plus running all\nexamples) in CI:\n\n| Platform | Architectures | \n|---|---|\n| Linux (glibc, musl) | `x86_64` ,`aarch64` | \n| macOS 13+ | `x86_64` ,`aarch64` | \n| iOS 13+ | `aarch64` | \n| FreeBSD | `x86_64` ,`aarch64` | \n| Windows | `x86_64` | \n| Android | `aarch64` ,`x86_64` ,`arm` | \n| WebAssembly | `wasm32` (freestanding) | \n\nThere is a second set of platforms we build in CI but do not run tests for. These systems all have known users; we just haven't set up the machinery for automated testing:\n\n| Platform | Architectures | \n|---|---|\n| Bare metal | `riscv32` ,`thumb` | \n| WebAssembly (WASI) | `wasm32` | \n| Windows | `arm64` | \n| illumos | `x86_64` | \n| 32-bit x86 | `x86` | \n\nEach of the tested platforms gets the artifacts it expects:\n\n- **Linux and FreeBSD** get a shared library with a proper SONAME and\nversioned symbols, a static library, headers, pkg-config files, and\na CMake package config.\n- **macOS and iOS** get a`dylib` with an`@rpath` install name and\ncompatibility version, plus an XCFramework covering macOS, iOS, and\nthe iOS simulator that drops straight into Xcode or Swift Package\nManager.\n- **Windows** gets a DLL with a`.pdb` , an import library, and a static\nlibrary. The library is built with the GNU ABI, but MSVC programs\nlink against it through the import library and CI verifies this.\n- **Android** gets a shared library built against the NDK with 16 KB\npage size support, as required by Android 15+.\n- **WebAssembly** ships in two flavors, one optimized for speed and one\nfor size, and the small one is under a megabyte with every feature\nenabled. If you only need a read-only viewer, subsystems like input\nencoding, search, selection, and Kitty graphics can be compiled out\nwith a build flag, which roughly halves the module. Every function\nstays exported and simply returns`GHOSTTY_UNSUPPORTED` so your code\ndoesn't have to change.<sup>[4](https://mitchellh.com#user-content-fn-3)</sup>\n\nPortability isn't just about the ability to build and run. It's also about resource usage and being able to work in a wide variety of resource environments.\n\nFor resource usage, the library creates no threads, allocates only through\nan allocator you can customize, and uses minimal compute and memory.\nI've run 10,000 active terminals, each with a live shell producing output,\non a Linux server with 4 cores and 8 GB of RAM. In this test, I had to use\n`dash` because `bash` used far more RAM than `libghostty-vt` and wouldn't fit\ninto the 8 GB budget.\n\n## \n\nLibghostty 1.0 is a major milestone.\n\nYou can now create a terminal in [~1,500 lines of C](https://github.com/ghostty-org/ghostling)\nthat has more features and better performance than just about any terminal\nthat existed in 2025, and most today in 2026.<sup>[5](https://mitchellh.com#user-content-fn-4)</sup> And thanks to the rich\necosystem of language bindings, you can do this in every major programming\nlanguage. You get this for free. For almost no effort. You can just do it.\n\n`libghostty-vt` is a generalized library, so we will focus on stability\nwhile implementing as many terminal protocols as exist\n(giving options to enable/disable them, of course) so that embedders\nhave the luxury of choice.\n\nEvery bug any `libghostty-vt` embedder reports makes everyone else in\nthe ecosystem better. Every feature we ship in `libghostty-vt` becomes\navailable to everyone quickly and safely. Terminals can move faster with\nless fragmentation.\n\nThank you to everyone who contributed to the library, wrote bindings, filed bugs, and shipped something on top of it while the API was still experimental. As with all open source, this was the work of a large community.\n\nDocs, examples, and downloads are at [lib.ghostty.org](https://lib.ghostty.org/).\n\nBoo. 👻\n\n## \n\n1. \nAs usual, I hate that I have to do this for every post, but I want to note this post was completely hand-written with no AI assistance. [↩](https://mitchellh.com#user-content-fnref-5)\n2. \nThe numbers are rough because most consumers don't report usage, but JetBrains alone reports [12.5 million recurring active users](https://www.jetbrains.com/lp/annualreport-2026/) ,\nand that's before counting everything else on the list.[↩](https://mitchellh.com#user-content-fnref-1)\n3. \nIn the original post I wrote \"not even libc!\" The default build does link libc, because the SIMD paths use it and the default allocator is `malloc` . Turn off SIMD and the library is freestanding, which is\nhow it runs on bare-metal RISC-V and ARM targets.[↩](https://mitchellh.com#user-content-fnref-2)\n4. \nThe feature flags aren't WASM-specific; they work on every target. They're likely useful for things like embedded devices too. [↩](https://mitchellh.com#user-content-fnref-3)\n5. \n\"Features\" here means the set of terminal protocols and sequences understood, and \"performance\" means parsing throughput and memory usage, since those are the parts `libghostty-vt` provides.[↩](https://mitchellh.com#user-content-fnref-4)","body_html":"<h1 id=\"mitchell-hashimoto\"><a href=\"https://mitchellh.com/\" rel=\"nofollow ugc noopener\">Mitchell Hashimoto</a></h1>\n<h1 id=\"libghostty-1-0\">Libghostty 1.0</h1>\n<p><code>libghostty-vt</code> 1.0 is here. <a href=\"https://lib.ghostty.org/\" rel=\"nofollow ugc noopener\">libghostty</a> is a\nportable, high-performance C library for terminal emulation, extracted\ndirectly from the core of Ghostty. The 1.0 release means both the library\nitself and the C ABI are now stable.</p>\n<p>A little over a year ago, I wrote that\n<a href=\"https://mitchellh.com/writing/libghostty-is-coming\" rel=\"nofollow ugc noopener\">libghostty is coming</a>. At the time,\nthe Zig module had just been merged, the C API didn&#39;t exist, and nobody\nbut Ghostty was a consumer. Today, the C API is a complete terminal emulator,\nit runs in production for millions of people across hundreds of products,\nboth free and commercial, and it has a real, enforced ABI stability policy.</p>\n<p>This post is about how we got here and what 1.0 actually means.<a href=\"https://mitchellh.com#user-content-fn-5\" rel=\"nofollow ugc noopener\">1</a></p>\n<p>## </p>\n<p>Since starting the Ghostty project in 2022, the most common question I&#39;ve\nbeen asked is &quot;why?&quot;. I already answered this in the\n<a href=\"https://mitchellh.com/writing/libghostty-is-coming\" rel=\"nofollow ugc noopener\">libghostty is coming</a>\npost, so feel free to read that if you wish. Today, I&#39;d rather answer this\nby showing the broad industry impact libghostty <em>has already had</em>. I believe\nthis strongly validates its existence.</p>\n<p>A year ago, I used a\n<a href=\"https://github.com/JetBrains/jediterm/pull/311\" rel=\"nofollow ugc noopener\">bug in JediTerm</a>,\nthe terminal emulator in JetBrains IDEs, as an example of why terminal\nemulation is hard to get right. A year later,\n<a href=\"https://blog.jetbrains.com/platform/2026/10/jetbrains-terminal-now-uses-ghostty/\" rel=\"nofollow ugc noopener\">the terminal in JetBrains IDEs now runs on libghostty</a>.\nEvery IntelliJ, PyCharm, GoLand, etc. user now has a libghostty-powered\nterminal. Based on a report by JetBrains, that&#39;s over 12.5 million\nactive users.</p>\n<p>Neovim has an <a href=\"https://github.com/neovim/neovim/pull/39773\" rel=\"nofollow ugc noopener\">approved pull request</a>\nreplacing libvterm with <code>libghostty-vt</code>. Among other things, it closes a\n<a href=\"https://github.com/neovim/neovim/issues/4997\" rel=\"nofollow ugc noopener\">10-year-old issue</a>\nabout reflowing scrollback on resize. The maintainers are waiting on a\ntagged release before merging so that distributions can package the\ndependency separately, and the release today should enable that.</p>\n<p>KDE developers are\n<a href=\"https://blogs.kde.org/2026/11/01/introducing-kwi/\" rel=\"nofollow ugc noopener\">experimenting with a Konsole replacement</a>\nbuilt on it. Vercel&#39;s Turborepo <a href=\"https://github.com/vercel/turborepo/pull/13135\" rel=\"nofollow ugc noopener\">uses it</a>\nto render task output in its TUI. <a href=\"https://devenv.sh/blog/2026/05/07/devenv-21-nix-with-zsh-fish-and-nushell-via-libghostty/\" rel=\"nofollow ugc noopener\">devenv</a>\nuses it to drive shells. Antithesis\n<a href=\"https://wickstrom.tech/2026-04-30-bombadil-terminal-experiment.html\" rel=\"nofollow ugc noopener\">used it to fuzz TUI programs</a>\nand found real bugs in btop and others. <a href=\"https://github.com/dakra/ghostel\" rel=\"nofollow ugc noopener\">Ghostel</a>\nbrings it to Emacs. <a href=\"https://github.com/coder/ghostty-web\" rel=\"nofollow ugc noopener\">ghostty-web</a>\nis the WASM build with an Xterm.js-compatible API. Commercial products\nlike <a href=\"https://orbstack.dev/\" rel=\"nofollow ugc noopener\">OrbStack</a> embed it. And a whole wave of\nnew terminals and &quot;agentic&quot; coding tools, such as\n<a href=\"https://github.com/herdrdev/herdr\" rel=\"nofollow ugc noopener\">herdr</a> and\n<a href=\"https://github.com/manaflow-ai/cmux\" rel=\"nofollow ugc noopener\">cmux</a>, have been built on it\nrather than writing yet another emulator.</p>\n<p>There are community bindings for Rust, Go, JavaScript, Swift, Python,\n.NET, Elixir, Dart, Java, and more, and the\n<a href=\"https://github.com/Uzaaft/awesome-libghostty\" rel=\"nofollow ugc noopener\">awesome-libghostty</a>\nlist tracks well over a hundred projects.</p>\n<p>More people today use a terminal powered by libghostty than use Ghostty\nthe application, by a very large multiple. And libghostty is having\na much larger impact than being &quot;just&quot; a terminal emulator.<a href=\"https://mitchellh.com#user-content-fn-1\" rel=\"nofollow ugc noopener\">2</a></p>\n<p>## </p>\n<p>1.0 means <code>libghostty-vt</code> follows semantic versioning and has strict\n<a href=\"https://en.wikipedia.org/wiki/Application_binary_interface\" rel=\"nofollow ugc noopener\">ABI compatibility</a>\npromises so that packagers across distributions and operating systems\ncan be confident packaging <code>libghostty-vt</code> and program developers can be\nconfident dynamically linking against it.</p>\n<p>Beyond providing useful features, I believe the hallmark of a high-quality and enduring C library is ABI stability. So from the start, I took inspiration from C libraries I enjoyed working with and designed the API to have a strong, stable ABI that allows for future additions.</p>\n<p>Every object is an opaque handle. The hundreds of values you might read or\nwrite go through a small set of enum-keyed getters and setters, so we\ncan add new values easily without introducing a new symbol. Programs with\nnewer headers linked against an older libghostty get <code>GHOSTTY_UNSUPPORTED</code>\nresults instead of crashes or undefined behavior. The few non-opaque structs\nwe have carry their size so that fields can be appended later, or contain\nreserved padding. Enums are pinned to <code>int</code> on every compiler, as much as\nthe C standard allows.</p>\n<p>Our CI enforces our ABI policy. Every change is checked with\n<a href=\"https://sourceware.org/libabigail/\" rel=\"nofollow ugc noopener\">libabigail</a> against a committed baseline\non Linux, and against golden type manifests on macOS and WebAssembly.</p>\n<p>On ELF platforms, every exported symbol is also versioned, so the dynamic loader refuses to load a mismatched library by name rather than failing in some mysterious way later.</p>\n<p>## </p>\n<p>In addition to ABI stability, the 1.0 release brings along the proper\nbuild tooling, tarballs, dependency licensing manifests, documentation,\nand more to enable every major operating system and distribution to\npackage <code>libghostty-vt</code> through standard official tooling.</p>\n<p>Libghostty has its own release cycle, separate from Ghostty the application. And it has its own tarballs with only the files and dependencies libghostty needs, resulting in smaller sizes and simpler licensing verification and compatibility.</p>\n<p>Each release publishes a signed source tarball along with a companion\ndependencies tarball containing every Zig package in Zig&#39;s own cache\nlayout, so a distribution can build the library completely offline. The\nbuild installs the shared and static libraries with a proper SONAME,\nheaders, pkg-config files, and a CMake package config, and it honors\n<code>--prefix</code>, <code>DESTDIR</code>, and <code>lib64</code>. Debug info is kept by default so\ndistros can split it out. All of this is documented in\n<a href=\"https://github.com/ghostty-org/ghostty/blob/main/PACKAGING-LIBGHOSTTY.md\" rel=\"nofollow ugc noopener\">PACKAGING-LIBGHOSTTY.md</a>,\nwhich ships with the tarball.</p>\n<p>## </p>\n<p><code>libghostty-vt</code> is MIT licensed. At runtime it needs nothing beyond\nlibc, and it can be built fully freestanding if you don&#39;t want that\neither.<a href=\"https://mitchellh.com#user-content-fn-2\" rel=\"nofollow ugc noopener\">3</a></p>\n<p>The library compiles in a small number of permissively licensed\ndependencies: <a href=\"https://github.com/simdutf/simdutf\" rel=\"nofollow ugc noopener\">simdutf</a> and\n<a href=\"https://github.com/google/highway\" rel=\"nofollow ugc noopener\">Google Highway</a> for SIMD, a compact\nUnicode table for grapheme data, and\n<a href=\"https://github.com/google/wuffs\" rel=\"nofollow ugc noopener\">Wuffs</a> for image decoding in the\nKitty graphics protocol. Both simdutf and Highway are built\n<a href=\"https://mitchellh.com/writing/simdutf-no-libcxx\" rel=\"nofollow ugc noopener\">without libc++</a>, so there is no C++\nstandard library dependency.</p>\n<p>There is no copyleft code anywhere in the dependency tree. Every dependency is listed in a machine-readable manifest with its version, SPDX license, and hash, specifically so distros can fill in their bundled-library metadata more easily.</p>\n<p>If a distro would rather dynamically link the system simdutf or Highway, there&#39;s a build flag for that.</p>\n<p>## </p>\n<p><code>libghostty-vt</code> is highly portable. The table below lists all the platforms\nand architectures that we build and test (full unit tests plus running all\nexamples) in CI:</p>\n<div class=\"table-wrap\"><table><thead><tr><th>Platform</th><th>Architectures</th></tr></thead><tbody><tr><td>Linux (glibc, musl)</td><td><code>x86_64</code> ,<code>aarch64</code></td></tr><tr><td>macOS 13+</td><td><code>x86_64</code> ,<code>aarch64</code></td></tr><tr><td>iOS 13+</td><td><code>aarch64</code></td></tr><tr><td>FreeBSD</td><td><code>x86_64</code> ,<code>aarch64</code></td></tr><tr><td>Windows</td><td><code>x86_64</code></td></tr><tr><td>Android</td><td><code>aarch64</code> ,<code>x86_64</code> ,<code>arm</code></td></tr><tr><td>WebAssembly</td><td><code>wasm32</code> (freestanding)</td></tr></tbody></table></div>\n<p>There is a second set of platforms we build in CI but do not run tests for. These systems all have known users; we just haven&#39;t set up the machinery for automated testing:</p>\n<div class=\"table-wrap\"><table><thead><tr><th>Platform</th><th>Architectures</th></tr></thead><tbody><tr><td>Bare metal</td><td><code>riscv32</code> ,<code>thumb</code></td></tr><tr><td>WebAssembly (WASI)</td><td><code>wasm32</code></td></tr><tr><td>Windows</td><td><code>arm64</code></td></tr><tr><td>illumos</td><td><code>x86_64</code></td></tr><tr><td>32-bit x86</td><td><code>x86</code></td></tr></tbody></table></div>\n<p>Each of the tested platforms gets the artifacts it expects:</p>\n<ul><li><p><strong>Linux and FreeBSD</strong> get a shared library with a proper SONAME and</p><p>versioned symbols, a static library, headers, pkg-config files, and\na CMake package config.</p></li><li><p><strong>macOS and iOS</strong> get a<code>dylib</code> with an<code>@rpath</code> install name and</p><p>compatibility version, plus an XCFramework covering macOS, iOS, and\nthe iOS simulator that drops straight into Xcode or Swift Package\nManager.</p></li><li><p><strong>Windows</strong> gets a DLL with a<code>.pdb</code> , an import library, and a static</p><p>library. The library is built with the GNU ABI, but MSVC programs\nlink against it through the import library and CI verifies this.</p></li><li><p><strong>Android</strong> gets a shared library built against the NDK with 16 KB</p><p>page size support, as required by Android 15+.</p></li><li><p><strong>WebAssembly</strong> ships in two flavors, one optimized for speed and one</p><p>for size, and the small one is under a megabyte with every feature\nenabled. If you only need a read-only viewer, subsystems like input\nencoding, search, selection, and Kitty graphics can be compiled out\nwith a build flag, which roughly halves the module. Every function\nstays exported and simply returns<code>GHOSTTY_UNSUPPORTED</code> so your code\ndoesn&#39;t have to change.&lt;sup&gt;<a href=\"https://mitchellh.com#user-content-fn-3\" rel=\"nofollow ugc noopener\">4</a>&lt;/sup&gt;</p></li></ul>\n<p>Portability isn&#39;t just about the ability to build and run. It&#39;s also about resource usage and being able to work in a wide variety of resource environments.</p>\n<p>For resource usage, the library creates no threads, allocates only through\nan allocator you can customize, and uses minimal compute and memory.\nI&#39;ve run 10,000 active terminals, each with a live shell producing output,\non a Linux server with 4 cores and 8 GB of RAM. In this test, I had to use\n<code>dash</code> because <code>bash</code> used far more RAM than <code>libghostty-vt</code> and wouldn&#39;t fit\ninto the 8 GB budget.</p>\n<p>## </p>\n<p>Libghostty 1.0 is a major milestone.</p>\n<p>You can now create a terminal in <a href=\"https://github.com/ghostty-org/ghostling\" rel=\"nofollow ugc noopener\">~1,500 lines of C</a>\nthat has more features and better performance than just about any terminal\nthat existed in 2025, and most today in 2026.&lt;sup&gt;<a href=\"https://mitchellh.com#user-content-fn-4\" rel=\"nofollow ugc noopener\">5</a>&lt;/sup&gt; And thanks to the rich\necosystem of language bindings, you can do this in every major programming\nlanguage. You get this for free. For almost no effort. You can just do it.</p>\n<p><code>libghostty-vt</code> is a generalized library, so we will focus on stability\nwhile implementing as many terminal protocols as exist\n(giving options to enable/disable them, of course) so that embedders\nhave the luxury of choice.</p>\n<p>Every bug any <code>libghostty-vt</code> embedder reports makes everyone else in\nthe ecosystem better. Every feature we ship in <code>libghostty-vt</code> becomes\navailable to everyone quickly and safely. Terminals can move faster with\nless fragmentation.</p>\n<p>Thank you to everyone who contributed to the library, wrote bindings, filed bugs, and shipped something on top of it while the API was still experimental. As with all open source, this was the work of a large community.</p>\n<p>Docs, examples, and downloads are at <a href=\"https://lib.ghostty.org/\" rel=\"nofollow ugc noopener\">lib.ghostty.org</a>.</p>\n<p>Boo. 👻</p>\n<p>## </p>\n<ol><li></li></ol>\n<p>As usual, I hate that I have to do this for every post, but I want to note this post was completely hand-written with no AI assistance. <a href=\"https://mitchellh.com#user-content-fnref-5\" rel=\"nofollow ugc noopener\">↩</a></p>\n<ol start=\"2\"><li></li></ol>\n<p>The numbers are rough because most consumers don&#39;t report usage, but JetBrains alone reports <a href=\"https://www.jetbrains.com/lp/annualreport-2026/\" rel=\"nofollow ugc noopener\">12.5 million recurring active users</a> ,\nand that&#39;s before counting everything else on the list.<a href=\"https://mitchellh.com#user-content-fnref-1\" rel=\"nofollow ugc noopener\">↩</a></p>\n<ol start=\"3\"><li></li></ol>\n<p>In the original post I wrote &quot;not even libc!&quot; The default build does link libc, because the SIMD paths use it and the default allocator is <code>malloc</code> . Turn off SIMD and the library is freestanding, which is\nhow it runs on bare-metal RISC-V and ARM targets.<a href=\"https://mitchellh.com#user-content-fnref-2\" rel=\"nofollow ugc noopener\">↩</a></p>\n<ol start=\"4\"><li></li></ol>\n<p>The feature flags aren&#39;t WASM-specific; they work on every target. They&#39;re likely useful for things like embedded devices too. <a href=\"https://mitchellh.com#user-content-fnref-3\" rel=\"nofollow ugc noopener\">↩</a></p>\n<ol start=\"5\"><li></li></ol>\n<p>&quot;Features&quot; here means the set of terminal protocols and sequences understood, and &quot;performance&quot; means parsing throughput and memory usage, since those are the parts <code>libghostty-vt</code> provides.<a href=\"https://mitchellh.com#user-content-fnref-4\" rel=\"nofollow ugc noopener\">↩</a></p>","headings":[{"level":1,"text":"Mitchell Hashimoto","id":"mitchell-hashimoto"},{"level":1,"text":"Libghostty 1.0","id":"libghostty-1-0"}]}}