Eugeny/tabby

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.