pickfit

BrowseLocal AI tools

TurboLLM

Runs local LLM engines auto-tuned to GPU with web UI and compatible API.

Use it

Before you install: known vulnerabilities

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

  • npm:brace-expansion 5.0.6 brace-expansion: DoS via exponential-time expansion of consecutive non-expanding {} groups (GHSA-3jxr-9vmj-r5cp, high, fixed in 5.0.7)
  • npm:undici 8.5.0 undici vulnerable to TLS certificate validation bypass via dropped tls options in Agent (GHSA-2m5v-pch6-74hx, high, fixed in 8.12.2)
See 8 more

3 more findings not listed here.

Linux x86_64

You need first

  • Runtimes: node>=22
  1. install turbollm globally via npm

    npm install -g turbollm

Check that it works

turbollm --help

The output should contain “--port <n>”.

First thing to try

turbollm --port 6996 --no-open --no-telemetry 2>&1
curl -s http://127.0.0.1:6996/api/v1/status

Run turbollm --port 6996 --no-open --no-telemetry to start the server, then open http://127.0.0.1:6996/ in a browser.

What it does

  • Chat with models in a web UI
    How to use it
    1. Start the server with turbollm --port 6996 --no-open --no-telemetry.
    2. Open http://127.0.0.1:6996/ in your browser to reach the TurboLLM web UI.
    Tested
  • Run any local LLM engine
    Not shown working
  • Tune engines to your GPU automatically
    Not shown working
  • Point Claude Code at your own machine
    Not shown working

How far pickfit got

Linux x86_64

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

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

Good for

  • Point Claude Code at your own machine
  • Browse and download GGUF models from Hugging Face
  • Copy the exact launch command for a loaded model

An alternative to LM Studio and Ollama.

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 1 Nov 2026
  • Version 1.15.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.