pickfit

BrowseDeveloper CLIs

Phantom

Open-source workbench connecting coding-agent accounts and local models for interactive and fleet engineering work.

Tested on macOS and LinuxKnown vulnerabilities

Use it

Before you install: known vulnerabilities

pickfit found 4 known high or critical vulnerabilities in the packages a fresh install brings (OSV.dev, 3 Nov 2026). Weigh this before you install it.

  • npm:@modelcontextprotocol/sdk 1.31.0 MCP TypeScript SDK: Experimental tasks were not tied to the session that created them (GHSA-22jm-h49p-29qw, high, fixed in 1.32.0)
  • npm:body-parser 2.3.0 body-parser vulnerable to Denial of Service via trailing bytes after a compressed request body (GHSA-27r3-jxmh-p828, high, fixed in 2.4.0)
See 2 more

macOS arm64

You need first

  • Runtimes: Node.js 22.15+
  • System packages: Git
  1. npm install -g @ashlr/phantom

    npm install -g @ashlr/phantom

Check that it works

phm --version

The output should contain “3.29.15”.

Linux x86_64

You need first

  • Runtimes: Node.js 22.15+
  • System packages: Git
  1. install phantom via npm

    npm install -g @ashlr/phantom

Check that it works

phm --version

The output should contain “3.29.15”.

First thing to try

phm verse --no-open --json
curl -s -o /tmp/verse.html -w "%{http_code} %{size_download}\n" http://127.0.0.1:7777/verse/ && head -c 2000 /tmp/verse.html; echo "---HEADERS---"; curl -s -D - -o /dev/null http://127.0.0.1:7777/verse/

What it does

  • Connect coding agent accounts and local models
    Not tested
  • Chat with agents and review their changes
    Not tested
  • Run an autonomous agent fleet toward a set outcome
    Not tested

How far pickfit got

macOS arm64

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

Linux x86_64

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

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

Good for

  • Describe work in a project and let Automatic choose an eligible connected resource
  • Save a desired result with observable acceptance for the fleet to work on
  • Start ollama serve for local model seats

How pickfit tested it

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

macOS arm64

Installs and starts

  • Replayed from scratch
  • Works offline
  • Checked on 1 Nov 2026
  • Version 3.29.15

Differences the test machine hit

  • README: source tree targets version 3.30.0
    In the test: npm latest is 3.29.15 at install time

Linux x86_64

Its service answers requests

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

Differences the test machine hit

  • README: `phm verse` starts the server and opens http://127.0.0.1:7777/verse/
    In the test: Run `phm verse --no-open --json` in background; it prints one JSON line with verseUrl and tokens and waits without opening a browser.
  • README: Source tree targets version 3.30.0 with canonical @ashlr/phantom release
    In the test: npm latest installed 3.29.15 while the source badge targets 3.30.0; pin @ashlr/phantom@<version> for reproducibility.

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.