Discofork
Repository brief

Eugeny/tabby

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-30T12:52:22.225Z
3mo ago

Eugeny/tabby

Tabby is a highly configurable terminal emulator and SSH/serial client for Windows, macOS, and Linux. It also includes telnet, SFTP, theming, split panes, tab restoration, plugin support, and a web app for SSH/SFTP/Telnet access. The repo is active, large, and heavily forked/starred, so forks are most interesting if you care about terminal UX, remote connection tooling, or plugin-driven customization.

GitHub
Loading tags...
Stars69,925
Forks3,921
Default branchmaster
Last pushed2026-03-20T12:48:52Z
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 only if its Windows-specific behavior and private-key vault changes are exactly what you need. If you want the newest Tabby features, translations, and lower maintenance risk, upstream is the safer choice.

Choose this fork only if its specific UI and compatibility tweaks matter more than staying current. For most users, upstream Tabby is the safer default because this fork is far behind and appears to have dropped a lot of localization and recent upstream work.

Prefer upstream unless you specifically need this exact older snapshot; this fork shows no added capability and is materially behind current Tabby.

Choose upstream Tabby unless you specifically need this fork's legacy Windows/Clink-focused customization. For most adopters, the fork is too stale and too far behind to be a good base.

Choose this fork only if its SFTP and SSH-specific tweaks are exactly what you need and you are comfortable carrying a stale codebase. For most users, upstream Tabby is the safer choice because this fork is materially out of date.

Adopt this only if you specifically need this older fork’s behavior or packaging. For most users, upstream Tabby is the better choice because this fork is stale and materially behind on features and fixes.

Choose this fork if Windows shell ergonomics and local customization matter more than staying current with upstream Tabby. Choose upstream if you want the newest fixes, plugin support, and lower maintenance risk.

Choose this fork only if its specific local patches are required. For most adopters, upstream Tabby is the safer choice because this fork is old, heavily diverged, and likely missing newer fixes and features.

Prefer this fork only if its config-level restrictions and older behavior are exactly what you need. For most adopters, upstream Tabby is the safer choice because this fork is dated, highly divergent, and likely missing many later fixes and workflows.

Prefer upstream unless you specifically want this exact snapshot. The fork shows no added functionality, is slightly behind, and looks like a maintenance mirror rather than a differentiated distribution.

Eugeny/tabby · Discofork