pickfit

BrowseDeveloper CLIs

VHS

A CLI tool that renders terminal sessions scripted in .tape files into GIFs, videos or text output for demos and integration testing.

Tested on LinuxKnown vulnerabilities

Use it

Before you install: known vulnerabilities

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

  • go:github.com/charmbracelet/wish v1.4.7 Wish has SCP Path Traversal that allows arbitrary file read/write (GHSA-xjvp-7243-rg9h, critical, no fix yet)

Linux x86_64

You need first

  • System packages: ttyd, ffmpeg
  1. Download the vhs v0.12.1 Linux x86_64 release binary into ~/.local/bin

    cd /tmp && V=$(curl -fsSL https://api.github.com/repos/charmbracelet/vhs/releases/latest | python3 -c 'import sys,json;print(json.load(sys.stdin)["tag_name"].lstrip("v"))') && curl -fsSLO https://github.com/charmbracelet/vhs/releases/download/v$V/vhs_${V}_Linux_x86_64.tar.gz && tar xzf vhs_${V}_Linux_x86_64.tar.gz && mkdir -p ~/.local/bin && cp vhs_${V}_Linux_x86_64/vhs ~/.local/bin/
  2. Install the ttyd and ffmpeg static binaries (README prerequisites) into ~/.local/bin

    cd /tmp && curl -fsSL -o ~/.local/bin/ttyd https://github.com/tsl0922/ttyd/releases/latest/download/ttyd.x86_64 && chmod +x ~/.local/bin/ttyd && curl -fsSLO https://github.com/BtbN/FFmpeg-Builds/releases/download/latest/ffmpeg-master-latest-linux64-gpl.tar.xz && tar xJf ffmpeg-master-latest-linux64-gpl.tar.xz && cp ffmpeg-master-latest-linux64-gpl/bin/ffmpeg ~/.local/bin/ && ffmpeg -version
Where the README and reality differ
  • README: VHS requires ttyd and ffmpeg
    What worked: VHS also downloads Chromium at runtime (go-rod, to ~/.cache/rod) on the first render, which needs network and system libraries (libnss3, libatk, libX11, libgbm, libcairo, libasound and more). Without them rendering fails with 'could not start browser'.

Check that it works

vhs --version

The output should contain “vhs version v0.12.1”.

First thing to try

(sleep 2; printf 'echo hello\r'; sleep 1; printf 'exit\r'; sleep 2) | timeout 30 script -qec "vhs record --shell bash" /dev/null

Run vhs record --shell bash to start recording a terminal session as a tape script.

What it does

  • Record terminal actions into a tape file
    How to use it
    1. Run vhs record --shell bash to start recording.
    2. Type your commands as usual, then type exit to stop.
    3. VHS prints the recorded actions as tape commands, such as Type "<your text>".
    Tested
  • Turn tape scripts into terminal GIFs
    Not tested
  • Publish GIFs to share them
    Not tested
  • Run the built-in SSH rendering server
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 1 of 4 features work
  4. Works offline

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

Good for

  • create a GIF demo of a CLI tool from a script
  • generate golden files for integration testing of terminal apps
  • keep demo GIFs updated in CI

How pickfit tested it

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

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 15 Nov 2026
  • Version v0.12.1 (24fa225)

Differences the test machine hit

  • README: Install with go install, pacman, nix, xbps, brew or apt (all need a toolchain, root or another distro)
    In the test: The release tarball vhs_0.12.1_Linux_x86_64.tar.gz from GitHub releases, copied to ~/.local/bin, plus static ttyd (tsl0922 releases) and ffmpeg (BtbN builds)
  • README: vhs record > cassette.tape
    In the test: It needs a real TTY: with no terminal it fails with 'inappropriate ioctl for device'. Running it under `script` worked.

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.