pickfit

BrowseDeveloper CLIs

Xolotl

Runs frontier MoE models like DeepSeek-V4.1-Flash 552B locally on one gaming PC with tiered VRAM/RAM/NVMe offloading.

How far pickfit got

pickfit hasn’t verified Xolotl yet, so there are no tested install steps.

What follows comes from its README only.

Use it

Before you install: known vulnerabilities

pickfit found 32 known high or critical vulnerabilities in the packages a fresh install brings (OSV.dev, 3 Nov 2026). Weigh this before you install it.

  • crates:zip 4.6.1 zip: Critical Parser Differential & Security Control Bypass via Dual-Header Inconsistencies (Zip Cloaking) Leading to Arbitrary File Overwrite & RCE (GHSA-m665-v7pm-7grj, critical, fixed in 9.0.5)
  • pypi:pillow 12.3.0 Pillow: Heap buffer overflow in _tiffWriteProc when saving TIFF to BytesIO (GHSA-332p-7hrc-92wf, critical, fixed in 13.0.0)
See 8 more

22 more findings not listed here.

You need first

  • Runtimes: cuda 12.x/13.x
  • System packages: cmake, ninja
  • Apple silicon only

What it does

pickfit hasn’t run it yet, so these come from the README only.

  • 512K context with 4-bit KV cache and speculative decoding
    Not tested
  • OpenAI and Anthropic compatible server for coding agents
    Not tested
  • Support for DeepSeek-V4.1, GLM-5.3-Flash and Qwen3.8 models in one engine
    Not tested

Good for

  • run DeepSeek-V4.1-Flash 552B as local coding agent on gaming PC
  • serve frontier MoE models via OpenAI/Anthropic-compatible API

An alternative to Strata.

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.