pickfit

BrowseLocal AI tools

Flyweight

Serves GGUF/safetensors LLMs from a native C++/CUDA runtime via OpenAI/Anthropic APIs.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Python 3.11+
  • A GPU is optional
  1. Install flyweight via uv tool

    uv tool install flyweight-llm

Check that it works

flyweight --version 2>&1

The output should contain “flyweight 0.25.0”.

First thing to try

flyweight doctor 2>&1

Run flyweight doctor first to check your setup.

What it does

  • Serve language models through compatible APIs
    Not tested
  • Chat with a model in the built-in web UI
    Not tested
  • Send images to a model as input
    Not tested
  • Generate images from text prompts
    Not tested

How far pickfit got

Linux x86_64

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

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

Good for

  • serve a GGUF model with chat UI and HTTP API
  • chat with a local model in the bundled chat UI
  • generate one response from a model and exit

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.25.0

Differences the test machine hit

  • README: flyweight serve model.gguf
    In the test: serve with --backend cpu and a model from a supported family (tested LiquidAI LFM2-350M Q4_0, 209 MB); the suggested stories260K test model is refused at load
  • README: CPU backend serves without a GPU
    In the test: generation of 16 tokens from LFM2-350M on the CPU backend did not finish within 300 s; /v1/models, /health and /props answer instantly

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.