pickfit

BrowseDeveloper CLIs

zhist

Records zsh commands with directory, exit status, and duration for fzf search.

Tested on Linux

Use it

Linux x86_64

You need first

  • System packages: fzf
  1. download linux_amd64 binary from GitHub releases and install to ~/.local/bin/zhist

    curl -L -o /tmp/zhist.tar.gz https://github.com/overflowy/zhist/releases/download/v1.2.2/zhist_1.2.2_linux_amd64.tar.gz && mkdir -p ~/.local/bin && tar xzf /tmp/zhist.tar.gz -C /tmp && cp /tmp/zhist ~/.local/bin/zhist && chmod +x ~/.local/bin/zhist && zhist init > /tmp/zhist_init_out.txt
Where the README and reality differ
  • README: CLI help via --help
    What worked: zhist --help returns 'unknown command'; top-level usage is bare 'zhist' (exit 2) and per-subcommand 'zhist init --help'

Check that it works

zhist init

The output should contain “zmodload zsh/datetime”.

First thing to try

zhist init

Run zhist init to set up zhist for your zsh shell.

What it does

These come from the README; pickfit didn’t check them one by one.

  • Record commands with their directory and exit status
    Not tested
  • Browse your history in an fzf picker
    Not tested
  • Switch between global and current-directory history
    Not tested
  • Search stored commands by prefix
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. Main function works
  4. Works offline

Good for

  • toggle between global and current-directory history
  • delete selected history entry
  • import existing zsh history file

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 31 Oct 2026

Differences the test machine hit

  • README: go install github.com/overflowy/zhist@latest
    In the test: box has no Go toolchain (go: command not found); installed prebuilt binary zhist_1.2.2_linux_amd64.tar.gz from GitHub releases to ~/.local/bin instead
  • README: Requires fzf 0.45 or newer for the picker
    In the test: core CLI (init, add, list, search, get, import) works without fzf; picker not tested in headless box

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.