pickfit

BrowseDeveloper CLIs

RustCode

Lightweight terminal coding agent that edits code using local and hosted models.

Tested on LinuxKnown vulnerabilities

Use it

Before you install: known vulnerabilities

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

  • crates:zip 2.4.2 zip: Critical Parser Differential & Security Control Bypass via Dual-Header Inconsistencies (Zip Cloaking) Leading to Arbitrary File Overwrite & RCE (GHSA-m665-v7pm-7grj, critical, fixed in 9.0.5)
  • crates:quinn-proto 0.11.17 Peer minimum ACK delay can panic quinn-proto when ACK_FREQUENCY transmission is enabled (RUSTSEC-2026-0340, high, fixed in 0.11.18)
See 4 more

Linux x86_64

  1. Download install script only

    curl -fsSL https://rustcode.lhagfoss.com/install.sh -o /tmp/install.sh
  2. Install rustcode via script

    bash /tmp/install.sh

Check that it works

rustcode --version

The output should contain “rustcode 0.112.1”.

First thing to try

rustcode doctor

Run rustcode doctor first to check your setup, then start the agent with rustcode.

What it does

  • Write code with any model provider
    Not tested
  • Edit files and run shell commands
    Not tested
  • Run background tasks and get their results
    Not tested
  • Start and manage child subagents
    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.

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 0.112.1

Differences the test machine hit

  • README: rustcode doctor
    In the test: doctor exits 1 when checks fail (missing keys, rg, tmux, skills dir) but still prints the check table; judge by output not exit 0

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.