pickfit

BrowseDeveloper CLIs

Detent

Board-driven orchestration that assigns ready board issues to coding agents in isolated worktrees.

Use it

Before you install: known vulnerabilities

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

  • go:github.com/labstack/echo/v4 v4.15.1 Echo: Rejected WebSocket upgrades can bypass Echo route-level access controls (GHSA-cxf3-9h37-7rr8, critical, fixed in 4.16.1)
  • go:github.com/getkin/kin-openapi v0.146.0 kin-openapi: ValidationHandler security-requirement bypass via encoded-path operation confusion (GHSA-23vg-4cjm-66q5, high, fixed in 0.147.0)
See 8 more

4 more findings not listed here.

Linux x86_64

You need first

  • Runtimes: Go 1.26, Node 24
  1. Download install script for reading

    curl -fsSL https://raw.githubusercontent.com/digitaldrywood/detent/main/install.sh -o /tmp/install-detent.sh && ls -l /tmp/install-detent.sh && wc -c /tmp/install-detent.sh
  2. Install Detent via read install script

    sh /tmp/install-detent.sh

Check that it works

detent --version

The output should contain “0.172.34”.

First thing to try

mkdir -p /tmp/detent-hub && DETENT_HUB_ADMIN_TOKEN=test-admin-token-12345 detent hub serve --database /tmp/detent-hub/hub.db --listen 127.0.0.1:7777 --github-disabled --headless
curl -s -H "Authorization: Bearer test-admin-token-12345" http://127.0.0.1:7777/

What it does

  • Run ready board issues on coding agents
    Not tested
  • Check agent results against gates
    Not tested
  • Land changes one at a time with a merge
    Not tested
  • Watch work on live dashboards
    Not shown working

How far pickfit got

Linux x86_64

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

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

Good for

  • Run a ready board issue on a coding agent in an isolated workspace
  • Validate agent changes against defined gates before landing
  • Land approved changes serially with a merge train
  • Monitor work live on web and terminal dashboards
  • Import GitHub issues for agent orchestration

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 30 Oct 2026
  • Version 0.172.34

Differences the test machine hit

  • README: curl -fsSL https://raw.githubusercontent.com/digitaldrywood/detent/main/install.sh | sh
    In the test: Downloaded to /tmp/install-detent.sh, read it with read_file, then ran sh /tmp/install-detent.sh
  • README: DETENT_HUB_ADMIN_TOKEN=... detent hub serve --database /var/lib/detent-hub/hub.db --listen 127.0.0.1:7777 --github-disabled
    In the test: Used --database /tmp/detent-hub/hub.db with DETENT_HUB_ADMIN_TOKEN=test-admin-token-12345 and --listen 127.0.0.1:7777 --github-disabled --headless
  • README: Hub serves web dashboard on listen address
    In the test: Dashboard root and /health required header Authorization: Bearer <admin-token>; unauthenticated request returns 401 unauthorized

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.