pickfit

BrowseDeveloper CLIs

hw-smi

Cross-compatible CPU/GPU telemetry monitor with ASCII visualization.

Tested on Linux

Use it

Linux x86_64

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. git clone the hw-smi source repository

    cd "$HOME"/work && git clone https://github.com/ProjectPhysX/hw-smi.git && cd hw-smi
  2. chmod +x make.sh and ./make.sh: compiles bin/hw-smi with g++ (no GPU drivers on this box, so the no-GPU build line ran)

    cd "$HOME"/work/hw-smi && chmod +x make.sh && ./make.sh
Where the README and reality differ
  • README: sudo bin/hw-smi --help
    What worked: --help prints the option list and then 'Press Enter to continue.' and waits for input; with stdin closed it did not exit (killed after 60 s, exit 137). Under timeout with SIGINT it continued into the monitor display instead of exiting, so it is not a clean non-interactive check.
  • README: writes all telemetry data into a file hw-smi-YYYY-DD-MM-hh-mm-ss.log located next to the hw-smi executable
    What worked: File written in bin/ next to the executable, named hw-smi-2026-11-16-05-15-54.log style: the date order is YYYY-MM-DD, not YYYY-DD-MM as the README says. The --help text says the file is hw-smi.log.
Verified in pickfit: the commands exactly as its sandbox ran them

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

cd /home/sbx/work && git clone https://github.com/ProjectPhysX/hw-smi.git && cd hw-smi
cd /home/sbx/work/hw-smi && chmod +x make.sh && ./make.sh
cd /home/sbx/work/hw-smi && timeout --preserve-status -s INT 5 bin/hw-smi --bars < /dev/null
cd /home/sbx/work/hw-smi && timeout --preserve-status -s INT 5 bin/hw-smi --bars < /dev/null

Check that it works

cd "$HOME"/work/hw-smi && timeout --preserve-status -s INT 5 bin/hw-smi --bars < /dev/null

The output should contain “Usage [”.

First thing to try

cd "$HOME"/work/hw-smi && timeout --preserve-status -s INT 5 bin/hw-smi --bars < /dev/null

What it does

  • Show CPU/GPU telemetry as ASCII bars
    Tested
  • Log telemetry data to a file
    Tested
  • Plot telemetry history as ASCII graphs
    Not tested
  • Show a graphical on-screen HUD on Windows
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 2 of 4 features work
  4. Works offline

Windows: the project says it runs there; pickfit hasn’t tried it.

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 16 Nov 2026

Differences the test machine hit

  • README: sudo bin/hw-smi --help / sudo bin/hw-smi --bars (run with sudo)
    In the test: Works without sudo on this box (no GPU, so only CPU/RAM metrics); README itself says it also works without sudo, sudo only matters for some Intel GPU counters.
  • README: hw-smi --bars / --graphs / --log are run interactively
    In the test: Both --bars and --graphs run until Enter/Ctrl+C; tested with timeout --preserve-status -s INT. Output is a continuous screen redraw.
  • README: Prerequisites: g++, ocl-icd-opencl-dev (and GPU drivers)
    In the test: For a build with no GPU driver found, make.sh compiled with plain g++ -std=c++17 -O3 and no OpenCL headers were needed; the box has no root so ocl-icd-opencl-dev was not installed. GPU driver support could not be built or tested here.

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.