pickfit

BrowseDeveloper CLIs

Termy

Fast native terminal with GPU-accelerated rendering, tabs, splits, and optional tmux sessions for macOS, Linux and Windows.

Use it

Before you install: known vulnerabilities

pickfit found 3 known high or critical vulnerabilities in the packages a fresh install brings (OSV.dev, 3 Nov 2026). Weigh this before you install it.

  • crates:quinn-proto 0.11.17 Peer minimum ACK delay can panic quinn-proto when ACK_FREQUENCY transmission is enabled (RUSTSEC-2026-0340, high, fixed in 0.11.18)
  • crates:rustls-webpki 0.103.9 rustls-webpki: Denial of service via panic on malformed CRL BIT STRING (GHSA-82j2-j2ch-gfr8, high, fixed in 0.103.13)
See 1 more

Linux x86_64

You need first

  • Runtimes: rust
  1. download Linux AppImage from GitHub Releases

    curl -fL -o /tmp/Termy.AppImage https://github.com/lassejlv/termy/releases/download/v1.0.0-rc.10/Termy-v1.0.0-rc.10-linux-x86_64.AppImage
  2. make AppImage executable

    chmod +x /tmp/Termy.AppImage

Check that it works

/tmp/Termy.AppImage --appimage-extract-and-run --version 2>&1

The output should contain “termy 1.0.0-rc.10”.

First thing to try

/tmp/Termy.AppImage --appimage-extract-and-run

What it does

  • GPU-accelerated rendering with damage-scoped dirty-span cell caching
    Not tested
  • Tabs, splits, search and reusable layouts for workspace management
    Not shown working
  • Optional tmux control-mode sessions
    Not shown working
  • Configurable keybindings, colors, themes and terminal behavior
    Not shown working

How far pickfit got

Linux x86_64

  1. Installs
  2. Opens
  3. 0 of 4 features work
  4. Works offline

macOS and Windows: the project says it runs there; pickfit hasn’t tried it.

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

It opens to its main screen

  • Replayed from scratch
  • Checked on 2 Nov 2026
  • Version 1.0.0-rc.10

When pickfit opened it, its main screen rendered. That shows it installs and starts; pickfit did not use any of its features. The launch passed again with the network off.

Differences the test machine hit

  • README: Build from source with cargo run --release -p termy (requires Rust)
    In the test: Pre-built Linux AppImage available on GitHub Releases (Termy-v1.0.0-rc.10-linux-x86_64.AppImage) runs with --appimage-extract-and-run, no toolchain needed

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.