pickfit

BrowseLocal AI tools

Narwhal

Disaggregated LLM inference framework that hot-swaps prefill and decode roles without reloading weights.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: python>=3.11
  • A GPU is required
  1. Install narwhal-inference with uv tool install

    uv tool install narwhal-inference
Where the README and reality differ
  • README: narwhal dev init then narwhal dev status
    What worked: Even after creating ~/.cache/huggingface and ~/.cache/huggingface/hub, `narwhal dev init` still exits 2 with FileNotFound for `~/.cache/huggingface/hub/models--Qwen--Qwen3.5-0.8B`; `narwhal dev status` without a prior successful init exits 2 with missing runs/dev/instance.json.

Check that it works

narwhal-serve --version

The output should contain “narwhal-inference 0.8.0”.

What it does

These come from the README; pickfit didn’t check them one by one.

  • Switch prefill and decode roles without reloading
    Not tested
  • Serve completion and chat requests
    Not tested
  • Profile engines and run benchmarks
    Not tested
  • Export metrics to Prometheus and Grafana
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. Not used yet
  4. Works offline

Good for

  • serve completion and chat requests streamed or buffered
  • reassign prefill and decode roles across GPU fleet
  • profile engines and run ordered benchmark points

How pickfit tested it

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

Linux x86_64

Installs and starts

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version 0.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.