pickfit

BrowseLocal AI tools

Llama GUI

Local launcher and control panel for configuring and running llama.cpp servers.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Python 3.9+
  1. Download online installer script for reading

    curl -fsSL https://raw.githubusercontent.com/thomas9120/LLama-GUI/main/online_installers/install-online.sh -o /tmp/install-online.sh
  2. Download installer sub-scripts for reading

    curl -fsSL https://raw.githubusercontent.com/thomas9120/LLama-GUI/main/install.sh -o /tmp/gui_install.sh && curl -fsSL https://raw.githubusercontent.com/thomas9120/LLama-GUI/main/mac_linux_start.sh -o /tmp/gui_start.sh
  3. Clone repo and install venv dependencies via installer

    LLAMA_GUI_NO_START=1 sh /tmp/install-online.sh
Where the README and reality differ
  • README: LLAMA_GUI_HOST=0.0.0.0 LLAMA_GUI_PORT=5240 python server.py
    What worked: use ~/LLama-GUI/.venv/bin/python server.py after ./install.sh creates the venv

Check that it works

curl -fsSL http://127.0.0.1:5240/api/status

The output should contain “available_backends”.

First thing to try

cd ~/LLama-GUI && LLAMA_GUI_HOST=0.0.0.0 LLAMA_GUI_PORT=5240 .venv/bin/python server.py
curl -fsSL http://127.0.0.1:5240/api/status

Start the server, then open http://127.0.0.1:5240 in your browser to reach the control panel.

What it does

  • Install prebuilt llama.cpp releases for your backend
    Not shown working
  • Launch llama-server or llama-cli
    Not tested
  • Chat with streaming Markdown replies and web search
    Not tested
  • Benchmark models with llama-bench and llama-perplexity
    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.

Good for

  • install prebuilt llama.cpp releases by backend
  • launch llama-server or llama-cli from Quick Launch or Configure
  • chat with streaming Markdown and optional web search
  • benchmark with llama-bench and llama-perplexity
  • manage launch presets and switch server presets

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 30 Oct 2026

Differences the test machine hit

  • README: no --version/--help documented; tool is a browser UI server
    In the test: server ignores --help and starts normally (had to be killed after 30s); no --version flag exists

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.