pickfit

BrowseDeveloper CLIs

Watchexec

A standalone command-line tool that watches a path and runs a command whenever it detects file modifications.

Tested on Linux

Use it

Linux x86_64

  1. Download v2.8.0 x86_64 musl prebuilt release tarball from GitHub and copy watchexec into ~/.local/bin

    mkdir -p ~/.local/bin /tmp/wx && cd /tmp/wx && URL=$(curl -fsSL https://api.github.com/repos/watchexec/watchexec/releases/latest | python3 -c 'import json,sys; d=json.load(sys.stdin); print([a["browser_download_url"] for a in d["assets"] if a["name"].endswith("x86_64-unknown-linux-musl.tar.xz")][0])') && curl -fsSLO "$URL" && tar xf *.tar.xz && cp */watchexec ~/.local/bin/

Check that it works

watchexec --version

The output should contain “watchexec 2.8.0”.

First thing to try

rm -rf /tmp/proj && mkdir -p /tmp/proj/sub/deep && cd /tmp/proj && git init -q && printf 'ignored.txt\n' > .gitignore && echo a > sub/deep/a.txt && echo b > sub/b.txt && echo i > ignored.txt && echo ok
cd /tmp/proj && (sleep 2; echo x >> sub/deep/a.txt) & cd /tmp/proj && timeout --preserve-status -s INT 5 watchexec --postpone -- echo F1-RAN-ON-CHANGE

From your project folder, run watchexec --postpone -- <command> to run a command each time a file changes.

What it does

  • Run a command when files in a folder change
    How to use it
    1. Open a terminal in your project folder.
    2. Run watchexec --postpone -- <command>.
    3. Edit any file in the folder or its subfolders and the command runs.
    Tested
  • Group many quick changes into one run
    How to use it
    1. Run watchexec --postpone -- <command> in your project folder.
    2. Save several files in quick succession. The command runs once for the batch.
    Tested
  • Skip files listed in .gitignore and .ignore
    How to use it
    1. List files to skip in your project's .gitignore.
    2. Run watchexec --postpone --emit-events-to=environment -- '<command>' in the project folder.
    3. Changes to ignored files do not trigger the command. Other changes do.
    Tested
  • Pass changed file paths to your command
    How to use it
    1. Run watchexec --postpone --emit-events-to=environment -- 'echo $WATCHEXEC_WRITTEN_PATH' to read the changed path from an environment variable.
    2. Or run watchexec --postpone --emit-events-to=json-stdio -- <command> to send each change as JSON to your command's standard input.
    Tested

How far pickfit got

Linux x86_64

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

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

Good for

  • automatically run unit tests on file changes
  • run linters or syntax checkers on change
  • rebuild artifacts when sources change
  • restart a Python server when Python files change

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 2.8.0

Differences the test machine hit

  • README: cargo binstall watchexec-cli / cargo install --locked watchexec-cli
    In the test: No Rust toolchain in the box; I used the README's other documented option, the prebuilt binary from GitHub releases (watchexec-2.8.0-x86_64-unknown-linux-musl.tar.xz)

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.