pickfit

BrowseDeveloper CLIs

mex

Shared project memory for engineers and AI agents that lives in the repo and is shared via Git.

Use it

Before you install: known vulnerabilities

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

  • npm:@simple-git/argv-parser 1.1.1 simple-git: `VISUAL` editor environment variable is omitted from unsafe editor detection (GHSA-v5rq-49vh-5v5c, critical, fixed in 2.0.1)
  • npm:simple-git 3.36.0 simple-git unsafe-operation guard does not block trailer command configuration (GHSA-x6jw-m9v5-85vh, critical, fixed in 4.0.1)
See 3 more

Linux x86_64

You need first

  • Runtimes: Node.js 22.5+
  • System packages: Git
  1. install mex-agent@0.8.5 globally via npm

    npm install -g mex-agent@0.8.5
Where the README and reality differ
  • README: npx mex-agent@0.8.5 setup completes setup then mex hub opens full Hub
    What worked: setup pauses after scaffold with exit 2 requiring population agent via `mex setup next --start` and manual Wiki population before Hub commit; fresh checkout only shows setup wizard with CSRF-protected API (401 without session)

Check that it works

mex --version

The output should contain “0.8.5”.

First thing to try

mex hub --no-open --port 8765

What it does

  • Store architecture, decisions and conventions as code-linked Wiki alongside code
    Not tested
  • Explore and review memory in local Project Hub
    Not shown working
  • Propose and review knowledge additions via Inbox
    Not tested
  • Create and share durable handoff Relays between teammates
    Not tested

How far pickfit got

Linux x86_64

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

Good for

  • share persistent project memory across engineers and AI agents via Git
  • pass work context between teammates with Relays

How pickfit tested it

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

Linux x86_64

Its service answers requests

  • Replayed from scratch
  • Works offline
  • Checked on 2 Nov 2026
  • Version 0.8.5

Differences the test machine hit

  • README: mex hub example runs directly
    In the test: hub requires prior scaffold; without it it runs setup wizard on 127.0.0.1 with one-time token link and CSRF protection

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.