pickfit

BrowseDeveloper CLIs

Pueue

A command-line tool with a background daemon that queues shell commands and runs long-running tasks sequentially or in parallel.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: stable Rust (for building from source or cargo)
  1. Download the prebuilt pueue and pueued musl binaries from the latest GitHub release into ~/.local/bin

    mkdir -p ~/.local/bin && curl -fsSL -o ~/.local/bin/pueue https://github.com/Nukesor/pueue/releases/latest/download/pueue-x86_64-unknown-linux-musl && curl -fsSL -o ~/.local/bin/pueued https://github.com/Nukesor/pueue/releases/latest/download/pueued-x86_64-unknown-linux-musl && chmod +x ~/.local/bin/pueue ~/.local/bin/pueued

Check that it works

pueue --version

The output should contain “pueue 4.0.4”.

First thing to try

pueued -v
pueue add 'ls $HOME && echo "Some string"' && pueue wait && pueue status && pueue log 0

Start the background daemon with pueued, then queue a command with pueue add '<your command>'.

What it does

  • Queue tasks and run several at once
    How to use it
    1. Start the daemon with pueued -v.
    2. Set how many tasks run at once with pueue parallel <number>.
    3. Queue commands with pueue add '<your command>', then check them with pueue status and pueue wait.
    Tested
  • Make a task wait for another task
    How to use it
    1. Queue the first task and get its ID with pueue add -p '<your command>'.
    2. Queue a dependent task with pueue add -p --after <task id> -- '<your command>'.
    3. Check progress with pueue status and see its output with pueue log <task id>.
    Tested
  • View task output and send input to tasks
    How to use it
    1. Queue a task that reads input with pueue add -p '<your command>'.
    2. Send it input with pueue send <task id> '<your text>'.
    3. See its output with pueue log <task id>.
    Tested
  • Sort tasks into groups with their own queues
    How to use it
    1. Create a group with pueue group add <group name> and set its limit with pueue parallel -g <group name> <number>.
    2. Add a task to it with pueue add -p -g <group name> '<your command>'.
    3. Check the group with pueue status -g <group name> and list groups with pueue group.
    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

  • queue long-running shell commands that keep running after SSH sessions end
  • run several tasks concurrently with a set parallelism limit
  • schedule a task to run at a specific time

An alternative to GNU Parallel, task-spooler, nq and pm2.

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 pueue 4.0.4

Differences the test machine hit

  • README: cargo install --locked pueue / build from source with cargo
    In the test: No Rust toolchain in the box; used the README's 'Prebuild Binaries' route instead: release assets pueue-x86_64-unknown-linux-musl and pueued-x86_64-unknown-linux-musl, renamed and placed on PATH
  • README: Use the pueue client (the README does not say how to start the daemon)
    In the test: Start the pueued daemon in the background first (here: pueued -v); the client talks to it over ~/.local/share/pueue/pueue_sbx.socket
  • README: Specify dependencies between tasks (no example given)
    In the test: --after takes several values, so `pueue add --after 3 'cmd'` fails with 'invalid digit found in string'; put `--` before the command: `pueue add --after 3 -- 'cmd'`
  • README: git clone git@github.com:Nukesor/pueue
    In the test: Cloning over SSH needs a GitHub SSH key; https://github.com/Nukesor/pueue works without one (not used here)

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.