pickfit

BrowseDeveloper CLIs

shep

Rust process manager whose daemon keeps long-running processes alive, restarts them, and captures output.

Tested on macOS and Linux

Use it

macOS arm64

You need first

  • System packages: Visual C++ redistributable
  1. Download prebuilt aarch64-apple-darwin archive and verify sha256

    mkdir -p ~/.local/bin /tmp/shep-dl && curl -fL -o /tmp/shep-dl/shep.tar.gz https://github.com/shep-pm/shep/releases/download/shep-v0.19.0/shep-aarch64-apple-darwin.tar.gz && curl -fL -o /tmp/shep-dl/shep.sha256 https://github.com/shep-pm/shep/releases/download/shep-v0.19.0/shep-aarch64-apple-darwin.sha256 && cat /tmp/shep-dl/shep.sha256 && (cd /tmp/shep-dl && shasum -a 256 shep.tar.gz) && tar tzf /tmp/shep-dl/shep.tar.gz
  2. Extract archive and install shep binaries to ~/.local/bin

    tar xzf /tmp/shep-dl/shep.tar.gz -C /tmp/shep-dl && install -m 755 /tmp/shep-dl/shep /tmp/shep-dl/shep-runtime /tmp/shep-dl/shep-dev ~/.local/bin/ && ls -l ~/.local/bin/shep* && ~/.local/bin/shep --version

Check that it works

shep --version

The output should contain “shep 0.19.0”.

First thing to try

shep welcome 2>&1

Run shep welcome to get started.

Linux x86_64

You need first

  • System packages: Visual C++ redistributable
  1. download and extract shep binary release

    curl -fsSL https://github.com/shep-pm/shep/releases/download/shep-v0.19.0/shep-x86_64-unknown-linux-gnu.tar.gz -o /tmp/shep.tar.gz && mkdir -p /tmp/shep_ex && tar -xzf /tmp/shep.tar.gz -C /tmp/shep_ex
  2. install shep binaries to local bin

    mkdir -p ~/.local/bin && cp /tmp/shep_ex/shep /tmp/shep_ex/shep-runtime /tmp/shep_ex/shep-dev ~/.local/bin/ && chmod +x ~/.local/bin/shep ~/.local/bin/shep-runtime ~/.local/bin/shep-dev && shep --version

Check that it works

shep --version

The output should contain “shep 0.19.0”.

First thing to try

shep welcome

Run shep welcome to get started.

What it does

  • Keep long-running processes alive
    How to use it
    1. List your apps with a name and script in a Flockfile.toml.
    2. Run shep start ./Flockfile.toml from that folder to start them under the daemon.
    Tested
  • Capture what your processes print
    How to use it
    1. Start your apps with shep start ./Flockfile.toml.
    2. Run shep bleats --no-follow --lines <number> to see recent output from each app.
    Tested
  • Restart processes when they die
    Not tested

How far pickfit got

macOS arm64

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

Linux x86_64

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

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

Good for

  • keep long-running processes alive and restart them when they die
  • capture what supervised processes print
  • follow aggregated process output logs
  • import pm2 saved process list into a Flockfile
  • let an agent host query the flock over Model Context Protocol

An alternative to pm2.

How pickfit tested it

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

macOS arm64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version 0.19.0

Differences the test machine hit

  • README: brew install shep-pm/shep/shep
    In the test: Used README prebuilt archive shep-aarch64-apple-darwin.tar.gz (v0.19.0) verified with .sha256 and installed shep, shep-runtime, shep-dev to ~/.local/bin
  • README: shep bleats --no-follow --lines 4 shows only app output
    In the test: bleats also prints notice[log_missing] lines for disabled built-in bark and metrics dogs

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version 0.19.0

Differences the test machine hit

  • README: cargo install shep
    In the test: used prebuilt release archive shep-x86_64-unknown-linux-gnu.tar.gz v0.19.0 from GitHub releases and copied shep, shep-runtime, shep-dev to ~/.local/bin
  • README: shep bleats --no-follow --lines 4 prints only sheep lines
    In the test: bleats still exits 0 and prints sheep output on stdout; missing bark/metrics log notices go to stderr

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.