pickfit

BrowseLocal AI tools

Helios

Readable PyTorch engine that serves Qwen3-4B locally with batching and paged attention.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: python>=3.11
  • A GPU is required
  • Needs the network
  1. Clone Helios source

    git clone https://github.com/sidmanale643/helios.git /tmp/helios-src
  2. Install dependencies with uv sync

    cd /tmp/helios-src && uv sync
Where the README and reality differ
  • README: uv sync
    What worked: Clone the repo first (git clone https://github.com/sidmanale643/helios.git) then run uv sync inside the clone; the work dir ships only README.md
  • README: Standard --version/--help CLI flags
    What worked: helios entrypoint is a server with no --version/--help flags; version confirmed via importlib.metadata (helios 0.1.0) and /health reports model and warmup_batch_sizes

Check that it works

cd /tmp/helios-src && ls -l .venv/bin/helios && .venv/bin/python -c "import importlib.metadata, torch; print('helios', importlib.metadata.version('helios')); print('torch', torch.__version__); print('cuda', torch.cuda.is_available())"

The output should contain “helios 0.1.0”.

First thing to try

cd /tmp/helios-src && ls -l .venv/bin/helios && .venv/bin/python -c "import importlib.metadata, torch; print('helios', importlib.metadata.version('helios')); print('torch', torch.__version__); print('cuda', torch.cuda.is_available())"

What it does

Good for

  • serve OpenAI-style chat completions locally
  • batch concurrent chat requests continuously
  • benchmark concurrent inference with timing data

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. Produces output
  4. Works offline

How pickfit tested it

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

Linux x86_64

It produces model output

  • Replayed from scratch
  • GPU: NVIDIA A10
  • Works offline
  • Checked on 1 Nov 2026
  • Version 0.1.0

Differences the test machine hit

  • README: First start downloads tokenizer and model weights
    In the test: Pre-download Qwen/Qwen3-4B snapshot (tokenizer.json + safetensors) with huggingface_hub snapshot_download before starting the server so the server reuses cache and never fetches during the check

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.