pickfit

BrowseLocal AI tools

gutsy

Local CPU decision model that returns calibrated probabilities for yes/no, choice, or score questions.

Tested on Linux

Use it

Linux x86_64

These steps ran from a folder named work in the home folder, which already existed. Make it and run them from there:

mkdir -p "$HOME/work" && cd "$HOME/work"
  1. git clone the gutsy repo (source for gutsy-inference)

    cd "$HOME"/work && git clone --depth 1 https://github.com/kouhxp/gutsy
  2. create venv in HOME and pip install -e gutsy-inference (builds llama-cpp-python 0.3.37 from source)

    python3 -m venv ~/gutsy-venv && ~/gutsy-venv/bin/pip install -e "$HOME"/work/gutsy/gutsy-inference
Verified in pickfit: the commands exactly as its sandbox ran them

For the record only: they name the sandbox's home, /home/sbx.

cd /home/sbx/work && git clone --depth 1 https://github.com/kouhxp/gutsy
python3 -m venv ~/gutsy-venv && ~/gutsy-venv/bin/pip install -e /home/sbx/work/gutsy/gutsy-inference
~/gutsy-venv/bin/gutsy-inference --help

Check that it works

~/gutsy-venv/bin/gutsy-inference --help

The output should contain “usage: gutsy-inference”.

What it does

  • Get calibrated probabilities for every option
    Not tested
  • Ask yes/no, choice and score questions
    Not tested
  • Choose among up to 255 options with reject
    Not tested
  • Ask cheap follow-up questions on one state
    Not tested

How far pickfit got

Linux x86_64

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

Good for

  • Triage a support ticket for team, refund and mood
  • Ask yes/no questions of feedback rows
  • Pick the cheapest model per message
  • Score each claim against a source
  • Detect live triggers on a sales call

An alternative to Laya and Jev.

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 16 Nov 2026

Differences the test machine hit

  • README: pip install -e gutsy/gutsy-inference # needs llama-cpp-python >= 0.3.35
    In the test: Installed into a venv under $HOME (python3 -m venv ~/gutsy-venv, then ~/gutsy-venv/bin/pip install -e). The plain pip command was not run here, so no claim is made about PEP 668 on this system Python. llama-cpp-python had no prebuilt wheel for this box and was compiled from source (about 3.5 minute…
  • README: hf download kouhxp/gutsy --include "gutsy-0.8b-v04*" --local-dir gutsy/gutsy-inference/models
    In the test: Not run. The model files are 505 MB (Q4_K_M) and 775 MB (Q8_0), above this box's ~300 MB download cap, so gutsy-inference check, serve and all README API examples were not run.

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.