pickfit

BrowseDeveloper CLIs

Range

Opens shells inside remote container images and datasets without downloading them first.

Tested on macOS and Linux

Use it

macOS arm64

You need first

  • Runtimes: Go 1.25 or newer
  • System packages: QEMU
  • A GPU is optional
  1. download and extract release binary range_Darwin_arm64.tar.gz

    curl -fsSL https://github.com/andreygrehov/range/releases/latest/download/range_$(uname -s)_$(uname -m).tar.gz | tar -xz && ls -lh range* 2>&1; ls -lh *.range 2>&1; file range
Where the README and reality differ
  • README: range --version
    What worked: range has no --version flag (exits 'unknown command --version'); use --help instead

Check that it works

./range --version 2>&1; echo "---"; ./range --help 2>&1

The output should contain “range — use a remote environment before downloading it”.

First thing to try

./range doctor 2>&1

Run ./range doctor first to check that your system is ready.

Linux x86_64

You need first

  • Runtimes: Go 1.25 or newer
  • System packages: QEMU
  • A GPU is optional
  1. download release tarball via curl and extract

    curl -fsSL https://github.com/andreygrehov/range/releases/latest/download/range_$(uname -s)_$(uname -m).tar.gz | tar -xz
  2. copy binary to ~/.local/bin on PATH

    mkdir -p ~/.local/bin && cp ./range ~/.local/bin/range && chmod +x ~/.local/bin/range
Where the README and reality differ
  • README: README shows curl | tar pipeline and ./range doctor, implies --version
    What worked: --version is unknown command; use --help; binary runs as ./range then needs move to ~/.local/bin

Check that it works

range --help

The output should contain “range — use a remote environment”.

First thing to try

mkdir -p /tmp/mydir3 && echo "hello world" > /tmp/mydir3/file.txt
range build /tmp/mydir3 -o /tmp/test3.range

Run ./range doctor first to check that your system is ready.

What it does

  • Build your own environment artifacts
    How to use it
    1. See the build options with ./range build --help.
    2. Build an artifact from a container image with ./range build --from-oci <image> -o <file>.range.
    Tested
  • Open a shell inside a remote image without downloading it
    Not tested
  • Run commands with mounts, ports and variables
    Not tested
  • Run isolated sessions with resource limits
    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. 1 of 4 features work
  4. Works offline

Good for

  • open a shell inside a container image
  • run a Python app with current directory mounted
  • run a server with published port and env variable

An alternative to Docker.

How pickfit tested it

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

macOS arm64

Its main function works

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

Differences the test machine hit

  • README: On a Mac with Apple silicon and macOS 14+ Range boots a small Linux VM with Virtualization.framework and range doctor says if host can run
    In the test: range doctor reported 'This host can run range shell' but every 'range run/shell' failed with VZErrorDomain Code=2 Virtualization is not available on this hardware (nested virtualization unavailable in this VM)

Linux x86_64

Its main function works

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

Differences the test machine hit

  • README: Prerequisites list Go 1.25 and QEMU/KVM
    In the test: binary install needs no Go; QEMU/root/nbd only needed at runtime, doctor reports MISSING root and nbd on sandbox

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.