pickfit

BrowseDeveloper CLIs

Plurnk

Terminal client for agentic coding with model-curated context and composable tools.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Node.js 26+
  • System packages: git
  • Keys or accounts: DEEPSEEK_API_KEY
  1. install Node 26 tarball

    curl -fsSL https://nodejs.org/dist/v26.13.0/node-v26.13.0-linux-x64.tar.xz -o /tmp/node26.tar.xz && tar -xJf /tmp/node26.tar.xz -C /tmp && cp -rf /tmp/node-v26.13.0-linux-x64/. ~/.local/
  2. install libatomic library

    curl -fsSL https://ftp.debian.org/debian/pool/main/g/gcc-14/libatomic1_14.2.0-19_amd64.deb -o /tmp/libatomic1.deb && mkdir -p /tmp/ladeb2 ~/.local/lib && dpkg-deb -x /tmp/libatomic1.deb /tmp/ladeb2 && cp -f /tmp/ladeb2/usr/lib/x86_64-linux-gnu/libatomic.so.1.2.0 ~/.local/lib/ && ln -sf libatomic.so.1.2.0 ~/.local/lib/libatomic.so.1
  3. install plurnk via npm

    LD_LIBRARY_PATH=$HOME/.local/lib npm install -g @plurnk/plurnk

Check that it works

LD_LIBRARY_PATH=$HOME/.local/lib plurnk --help

The output should contain “subcommands:”.

First thing to try

LD_LIBRARY_PATH=$HOME/.local/lib plurnk models

Run plurnk models first to see which local or cloud models are available.

What it does

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

  • Let the model choose what context to keep
    Not tested
  • Read back and manage saved memory
    Not tested
  • Explore and edit project files by pattern
    Not tested

How far pickfit got

Linux x86_64

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

Good for

  • build software using local or cloud models
  • investigate a codebase
  • summarize a repository to a 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 30 Oct 2026
  • Version 4.3.0

Differences the test machine hit

  • README: Requirements: Node.js 26+
    In the test: Installed Node v26.13.0 from nodejs.org linux-x64 tarball into ~/.local (shadows /usr/local/bin/node v22.23.4); npm install warns EBADENGINE under Node 22 and plurnk exits 1 requiring Node 26
  • README: npm install -g @plurnk/plurnk works on Linux
    In the test: Fetched libatomic1_14.2.0-19_amd64.deb from ftp.debian.org, copied libatomic.so.1* to ~/.local/lib and run all node/plurnk commands with LD_LIBRARY_PATH=$HOME/.local/lib
  • README: plurnk models lists available model routes
    In the test: plurnk models exits 0 with '(no models match; use --all to include models missing local configuration)' and auto-starts plurnk-service daemon when no API keys are configured

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.