What JusTTY Does Not Do
JusTTY does not expose:
- Splits and panes. One terminal per tab. Use tabs, or a multiplexer like tmux inside a tab.
- An inspector. No debug surface for the terminal state.
- Custom
ghostty.confor profiles. The host builds its own configuration; your Ghostty config is not read. See Architecture. - Remappable shortcuts in the UI. The bindings in Keyboard Shortcuts are the bindings.
- Sandboxed or in-memory backends. The app sandbox stays off so Ghostty can spawn real login shells.
Why#
JusTTY targets quick commands, not full Ghostty parity. Every option that is not there is an option nobody has to read past on their way to a shell prompt. The renderer, VT handling, and search are Ghostty's, so what you lose is configuration surface, not terminal quality.
When to use something else#
If you live in splits, want a per-project profile system, or need to rebind keys to match muscle memory from another terminal, run Ghostty directly. It is the same engine with all of its configuration intact.
If you want a terminal that opens fast, renders well, and asks nothing of you, stay here. Start with Install JusTTY.