pickfit

BrowseLocal AI tools

llama-buddy

CLI wrapper to manage, download, and serve local LLMs via llama-server.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: python>=3.10
  • System packages: llama-server
  1. uv tool install llama-buddy

    uv tool install llama-buddy

Check that it works

llb status 2>&1

The output should contain “llama-server is not running.”.

First thing to try

llb status 2>&1

Run llb status to see the current state of your local models and server.

What it does

  • Manage, download, and serve local LLMs
    Not shown working
  • Run llama-server in the background
    Not tested
  • Search HuggingFace and download models
    Not shown working
  • Chat with a model interactively
    Not shown working

How far pickfit got

Linux x86_64

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

Good for

  • download a GGUF model from HuggingFace
  • start llama-server in the background
  • chat with a model via llama-cli
  • inspect GGUF model metadata
  • list local models with VRAM usage

An alternative to ollama.

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 31 Oct 2026
  • Version 0.1.16

Differences the test machine hit

  • README: Prerequisite: llama.cpp installed and llama-server on PATH
    In the test: install succeeds without llama-server, but llb start fails with 'llama-server not found. Please install llama.cpp.'; wrapper works but serve/chat need binary
  • README: llb models shows table of models
    In the test: without running server exits 1 with 'Could not connect to llama-server. Is it running?' rather than empty table

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.