pickfit

BrowseLocal AI tools

Xyntetik Runner

Single-binary C GGUF engine that serves models and trains LoRA adapters locally.

Tested on macOS and Linux

Use it

macOS arm64

  1. Download macOS arm64 binary from GitHub releases

    curl -LO https://github.com/Joakimpalm-Zen/xyntetik-runner/releases/latest/download/runner-macos-arm64 && chmod +x runner-macos-arm64 && mv runner-macos-arm64 runner && ls -lh runner
    
  2. Download tiny GGUF model stories260K for testing

    mkdir -p ~/models && curl -fL -o ~/models/stories260K.gguf https://huggingface.co/ggml-org/test-model-stories260K/resolve/main/stories260K-f32.gguf && ls -lh ~/models/stories260K.gguf

Check that it works

./runner --version

The output should contain “runner 1.10.0”.

First thing to try

./runner --info caps

Run ./runner --info caps to see what the engine supports on your machine.

Linux x86_64

  1. download Linux binary and checksums with verification

    curl -fL -o runner-linux-x86_64 https://github.com/Joakimpalm-Zen/xyntetik-runner/releases/latest/download/runner-linux-x86_64 && curl -fL -o SHA256SUMS https://github.com/Joakimpalm-Zen/xyntetik-runner/releases/latest/download/SHA256SUMS && sha256sum -c --ignore-missing SHA256SUMS
  2. make executable, rename to runner

    chmod +x runner-linux-x86_64 && mv runner-linux-x86_64 runner && ./runner --version

Check that it works

./runner --info caps 2>&1

The output should contain “architectures”.

First thing to try

./runner --info caps 2>&1

Run ./runner --info caps to see what the engine supports on your machine.

What it does

  • Serve a model through an OpenAI-compatible API
    How to use it
    1. Start the server with ./runner -m <model.gguf> --serve --port 8080.
    2. Send a chat request with `curl -s http://127.0.0.1:8080/v1/chat/completions -H 'Content-Type: application/json' -d '{"messages":[{"role":"user","content":"<your text>"}],"temperature":0,"max_tokens":1
    Tested
  • Train a LoRA adapter through quantized weights
    Not tested
  • Finish tool calls past the token limit
    Not tested
  • Record a run as a signed receipt and replay it
    Not tested

How far pickfit got

macOS arm64

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

Linux x86_64

  1. Installs
  2. Starts
  3. 3 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 via OpenAI-compatible HTTP API
  • check whether a model fits before downloading
  • quantize model file with custom type plan
  • train LoRA adapter through quantized weights
  • verify signed reproducible inference receipt

An alternative to llama.cpp, vLLM, Ollama, TensorRT-LLM and SGLang.

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

macOS arm64

It produces model output

  • Replayed from scratch
  • Works offline
  • Checked on 1 Nov 2026
  • Version 1.10.0

Differences the test machine hit

  • README: Published release 1.6.1
    In the test: Downloaded binary reports 1.10.0, still compatible

Linux x86_64

It produces model output

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version runner 1.8.0

Differences the test machine hit

  • README: git clone + make; quick-start shows runner-macos-arm64
    In the test: used MANUAL Linux asset runner-linux-x86_64 + SHA256SUMS with sha256sum -c; no compiler or make in box so source build impossible and macOS asset cannot run on Linux
  • README: ./runner --version -> runner 1.6.1
    In the test: binary printed runner 1.8.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.