pickfit

BrowseLocal AI tools

Bittune

Local agent that deploys and benchmarks vLLM/SGLang inference on your GPUs with auditable evidence.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Python >= 3.10, Node.js >= 22.19.0
  • System packages: OpenSSL CLI
  • A GPU is optional
  • Keys or accounts: BITTUNE_AGENT_LLM_API_KEY

step 4 still names /home/sbx inside single quotes, where $HOME would not work: put your own home folder there before running it.

These steps ran from a folder named work in the home folder, which already existed. Make it and run them from there:

mkdir -p "$HOME/work" && cd "$HOME/work"
  1. clone Bittune source

    git clone --depth 1 https://github.com/bitcloud-ai/Bittune bittune-src
  2. npm ci plus venv Python Core install

    cd bittune-src && npm ci && python3 -m venv .venv && .venv/bin/python -m pip install -e ./packages/bittune-core && .venv/bin/python -c "import bittune_core; print('core ok')"
  3. build portable dist bundle

    cd bittune-src && npm run build:shell
  4. install bittune shim on PATH

    mkdir -p ~/.local/bin && printf '%s\n' '#!/bin/sh' 'export BITTUNE_CORE_PYTHON="/home/sbx/work/bittune-src/.venv/bin/python"' 'export BITTUNE_TEST_PYTHON="/home/sbx/work/bittune-src/.venv/bin/python"' 'exec node "/home/sbx/work/bittune-src/dist/bittune.js" "$@"' > ~/.local/bin/bittune && chmod +x ~/.local/bin/bittune
Where the README and reality differ
  • README: npm ci; python3 -m venv .venv; pip install -e ./packages/bittune-core; npm run bittune
    What worked: After npm ci plus venv pip install, also ran npm run build:shell and installed a ~/.local/bin/bittune shim that sets BITTUNE_CORE_PYTHON/BITTUNE_TEST_PYTHON to the venv python and execs node dist/bittune.js; direct tsx entry fails outside the repo with Cannot find package 'tsx'
Verified in pickfit: the commands exactly as its sandbox ran them

For the record only: they name the sandbox's home, /home/sbx.

git clone --depth 1 https://github.com/bitcloud-ai/Bittune bittune-src
cd bittune-src && npm ci && python3 -m venv .venv && .venv/bin/python -m pip install -e ./packages/bittune-core && .venv/bin/python -c "import bittune_core; print('core ok')"
cd bittune-src && npm run build:shell
mkdir -p ~/.local/bin && printf '%s\n' '#!/bin/sh' 'export BITTUNE_CORE_PYTHON="/home/sbx/work/bittune-src/.venv/bin/python"' 'export BITTUNE_TEST_PYTHON="/home/sbx/work/bittune-src/.venv/bin/python"' 'exec node "/home/sbx/work/bittune-src/dist/bittune.js" "$@"' > ~/.local/bin/bittune && chmod +x ~/.local/bin/bittune
bittune --help
bittune version

Check that it works

bittune --help

The output should contain “Usage:”.

First thing to try

bittune version

Run bittune version in a terminal to confirm the tool starts, then launch bittune to open the interface.

What it does

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

  • Deploy and manage vLLM or SGLang services
    Not tested
  • Check your GPU setup and find models
    Not tested
  • Benchmark services and save the results
    Not tested
  • Record tuning experiments and compare candidates
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. Main function works
  4. Works offline

Good for

  • Deploy Qwen model to vLLM and benchmark throughput
  • Inspect GPU machine and generate hardware snapshot
  • Compare benchmark results with deterministic deltas

How pickfit tested it

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

Linux x86_64

Its main function works

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

Differences the test machine hit

  • README: tar -xzf bittune-<version>-linux-x86_64.tar.gz; cd bundle; sudo ./install.sh
    In the test: Skipped ranked sudo ./install.sh and installed from source because the box has no root/sudo and install.sh installs to /usr/local/bin and /opt/bittune
  • README: export BITTUNE_AGENT_LLM_API_KEY='your-api-key'; bittune configure --base-url https://endpoint.example.com/v1 --model-id your-tool-capable-model; bittune doctor
    In the test: bittune doctor exits 0 with a dummy OpenAI-compatible base-url and BITTUNE_AGENT_LLM_API_KEY=dummy, reporting Python Core and Runtime assembled without any real endpoint, Docker, GPU, or EvalScope

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.