pickfit

BrowseDeveloper CLIs

Nimbus

Local-first AI agent that gives DevOps teams on-call incident context over their tools.

Tested on Linux

Use it

Linux x86_64

You need first

  • System packages: libsecret-tools, bubblewrap
  1. download install.sh script

    curl -fsSL https://github.com/nimbus-agent/Nimbus/releases/latest/download/install.sh -o /tmp/install.sh && ls -lh /tmp/install.sh && head -n 200 /tmp/install.sh
  2. run install.sh --yes installs to ~/.local/bin

    sh /tmp/install.sh --yes

Check that it works

nimbus --version 2>&1

The output should contain “10.13.0”.

What it does

  • Get incident context across services
    Not tested
  • Trace where each line of code came from
    Not tested
  • Run automation plans that need your consent
    Not tested
  • See a record of what data left your machine
    Not tested

How far pickfit got

Linux x86_64

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

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

Good for

  • get incident context for a firing alert
  • trace line-level provenance for a file
  • check release readiness for open PRs
  • correlate security alerts with codebase
  • prove what left the machine via egress ledger

How pickfit tested it

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

Linux x86_64

Installs and starts

  • Replayed from scratch
  • Works offline
  • Checked on 31 Oct 2026
  • Version 10.13.0

Differences the test machine hit

  • README: Linux .deb installs bubblewrap and libcap2-bin via apt; script warns if bubblewrap missing
    In the test: Gateway fails without bubblewrap and libsecret-tools (secret-tool): doctor shows [fail] Vault and Sandbox, init exits 2
  • README: curl | sh install needs gpg for signature
    In the test: Installer printed SIGNATURE NOT CHECKED when gpg missing, installed on sha256 only

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.