Discofork
Repository brief

ghostty-org/ghostty

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T11:52:47.123Z
3mo ago

ghostty-org/ghostty

Ghostty is an active, widely used open source terminal emulator with a strong upstream: 49,142 stars, 2,168 forks, and recent commits on March 29-30, 2026. The project emphasizes native platform UI, GPU acceleration, standards-compliant terminal emulation, and an embeddable cross-platform library (`libghostty`).

GitHub
Loading tags...
Stars49,142
Forks2,168
Default branchmain
Last pushed2026-03-30T00:19:08Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose this fork if you want a macOS terminal built around worktrees, vertical tabs, and integrated git/agent workflows. Choose upstream Ghostty if you want the broadest platform support, freshest fixes, and a general-purpose terminal with lower maintenance risk.

Choose this fork if the sidebar-first macOS tab experience is the priority. Stick with upstream if you want the latest Ghostty fixes, broader platform parity, and lower maintenance risk.

Choose this fork only if macOS 12 compatibility is the main requirement. For everyone else, upstream Ghostty is the better default because this fork is materially stale and likely missing a large amount of recent correctness and feature work.

Prefer this fork if your priority is Windows and GTK workflow polish, especially shell replacement, passthrough, and process cleanup. Prefer upstream if you want the freshest Ghostty fixes, broader platform parity, and lower maintenance risk.

Choose this fork if macOS terminal search is the main pain point you want solved. Choose upstream if you want the newest Ghostty fixes, platform support, and library changes more than the Cmd+F workflow.

Choose this fork if the added terminal workflow hooks and macOS polish matter more than staying close to upstream. Choose upstream if you want the newest Ghostty fixes, lower maintenance burden, and the broadest compatibility.

Prefer upstream Ghostty unless you specifically need this older snapshot; the fork adds no visible capabilities and is materially behind on fixes and platform work.

Choose this fork if your priority is a native Windows Ghostty experience with ConPTY, Win32 UI, and split/tab workflows. Avoid it if you need close upstream parity or broad platform support, because it is already noticeably behind and is purpose-built for Windows divergence.

Prefer upstream unless you specifically need this exact older snapshot; the fork adds nothing and is far behind on fixes, compatibility work, and examples.

Choose this fork only if you want a clean old baseline; for normal adoption, upstream is clearly preferable because this fork has no added features and is far behind current Ghostty.