Resume
← Blog

2026.11.08 · 4 min · open source · webassembly · javascript · tooling · news

libghostty: one terminal engine, everywhere.

libghostty-vt 1.0 turns Ghostty's terminal core into a stable, MIT-licensed C library. It already runs every JetBrains IDE terminal, a Neovim PR wants it, and ghostty-web puts it in the browser. What the engine does, what it doesn't, and how to try it. As of 2026.11.

Every terminal you use, in your IDE, your editor or a web dashboard, has to decode the same escape codes. Older engines skip the newer ones, which is why Claude Code, Neovim or tmux can glitch inside an IDE terminal. This week libghostty-vt hit 1.0: Ghostty's terminal core as a stable C library, so one engine can sit inside all of them and a fix lands in every app at once.

Watch the 60-second version on Instagram.

What 1.0 covers

1.0 is libghostty-vt, the terminal emulation part, and its C ABI. In Mitchell Hashimoto's words, "the library itself and the C ABI are now stable."

  • Semver with strict ABI checks. Every object is an opaque handle, and a newer header against an older library returns GHOSTTY_UNSUPPORTED instead of crashing.
  • MIT licensed, needs only libc at runtime, no copyleft anywhere in its dependencies.
  • An official Wasm build: "the small one is under a megabyte with every feature enabled."
  • Tested in CI on Linux, macOS, iOS, Windows, Android, FreeBSD and wasm32.

What it is not: the Ghostty app. There's no window and no renderer. libghostty reads the escape codes and keeps the screen state; the host draws the screen.

\x1b[31merror\x1b[0mBYTESLIBGHOSTTY-VTPARSE + STATEHOST RENDERERYOU DRAW ITNO WINDOW · NO RENDERER · ONLY LIBC AT RUNTIMEFIG. 01 / PARSE AND STATE, NOT PIXELS

Where it runs

LIBGHOSTTY-VT1.0 · C ABI · MITJETBRAINS IDESHIPPED · 2026.3NEOVIM :terminalPR OPEN · NOT MERGEDBROWSER TABGHOSTTY-WEB · NPMFIG. 02 / ONE ENGINE, THREE HOSTS
HostStatus
JetBrains IDEsShipped. On by default in 2026.3, replacing JediTerm
Neovim :terminalPR #39773, open, not merged
Browser (ghostty-web)On npm today

JetBrains. The IDEs replaced JediTerm with libghostty. It's on by default in 2026.3, handles about 50 control sequences JediTerm ignored or misread, and can be switched off with the registry key terminal.use.ghostty.emulator. JetBrains still does the rendering. Mitchell Hashimoto says it "powers all JetBrains IDE terminals, over 12.5 million active users." Not wired up yet: clipboard writes, notifications and inline images.

Neovim. PR #39773 replaces libvterm with libghostty-vt in :terminal. It's a PR, not a release: an earlier version got an approval in May 2026, and the maintainers wanted a tagged libghostty release first. They plan to merge after Neovim 0.13 and the Zig 0.17 update.

Others already on it: Turborepo, OrbStack, devenv, Ghostel (Emacs), cmux, and a Konsole experiment.

Try it in the browser

ghostty-web is Coder's project (built for Mux), MIT, with a ~400 KB Wasm bundle and zero runtime dependencies. It "aims to be API-compatible" with xterm.js, so it's nearly a drop-in: swap the import and add await init().

terminal.js
- import { Terminal } from '@xterm/xterm';
+ import { init, Terminal } from 'ghostty-web';
+ await init(); // loads the Wasm engine
 
const term = new Terminal({ fontSize: 14 });
term.open(document.getElementById('terminal'));
term.onData((d) => socket.send(d));
socket.onmessage = (e) => term.write(e.data);

Two caveats. ghostty-web currently builds from a patched Ghostty source; it plans to move to the official Wasm build but doesn't ship the 1.0 artifact yet. And its demo starts a real local shell, so never expose it remotely.

On a client project with an xterm.js panel, I'd try the swap on a branch and run the TUIs our users actually run (Claude Code, Neovim, tmux) through both before switching.

The full how-to (browser, JetBrains, embedding the C library) is on the libghostty page.

What people get wrong

  • "libghostty is the Ghostty app." It's only the engine: no window, no renderer. Each host draws the screen itself.
  • "Neovim uses it." A Neovim PR does. It's open and unmerged.
  • "ghostty-web is a drop-in." Nearly: compatibility is a goal, and you need await init().
  • "xterm.js is xterm." Different projects. xterm.js is the browser library ghostty-web wants to replace.

The short version

  1. libghostty-vt 1.0 is Ghostty's terminal core as a stable, MIT-licensed C library with a stable ABI.
  2. It parses escape codes and keeps screen state; the host still draws.
  3. Every JetBrains IDE terminal runs on it as of 2026.3; a Neovim PR is open.
  4. In the browser, ghostty-web is nearly a drop-in for xterm.js: swap the import, await init().
  5. One shared engine means a fix lands in every terminal that uses it.

Sources: Mitchell Hashimoto, libghostty 1.0 · JetBrains Blog, The Terminal in JetBrains IDEs Now Runs on libghostty · neovim/neovim PR #39773 · coder/ghostty-web README · Hacker News discussion · iThome, JetBrains 2026.3 EAP report