pickfit

BrowseDeveloper CLIs

wtfi2

Live visual tool that traces the network path to pinpoint where a connection fails and how to fix it.

Use it

Before you install: known vulnerabilities

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

  • crates:quinn-proto 0.11.16 Peer minimum ACK delay can panic quinn-proto when ACK_FREQUENCY transmission is enabled (RUSTSEC-2026-0340, high, fixed in 0.11.18)
See 1 more

Linux x86_64

You need first

  • Runtimes: Rust 1.88+
  • System packages: ip, iw, ping, traceroute
  • Needs the network
  1. download installer script from GitHub releases

    curl --proto '=https' --tlsv1.2 -LsSf https://github.com/kanywst/wtfi2/releases/latest/download/wtfi2-installer.sh -o /tmp/wtfi2-installer.sh
  2. run installer script to install wtfi binary to ~/.cargo/bin

    sh /tmp/wtfi2-installer.sh
  3. symlink wtfi to ~/.local/bin so it is on PATH

    ln -sf ~/.cargo/bin/wtfi ~/.local/bin/wtfi && export PATH="$HOME/.local/bin:$PATH" && wtfi --version

Check that it works

export PATH="$HOME/.cargo/bin:$PATH" && wtfi --version; echo ---; wtfi --help

The output should contain “wtfi 0.9.0”.

First thing to try

timeout 4 wtfi -w --no-color

Run wtfi to trace your connection and see where it fails.

What it does

  • Find where your Wi-Fi connection fails
    How to use it
    1. Run wtfi --no-color to see which hop on the path is failing.
    2. Run wtfi -v --no-color for details on hops that could not be measured.
    Tested
  • See your connection as a path diagram
    How to use it
    1. Run wtfi --no-color to print the path from You through Wi-Fi, Gateway, Internet, DNS and Portal, with a mark for each hop.
    Tested
  • Get the root cause and a fix
    How to use it
    1. Run wtfi --json and read the "headline" field for the diagnosis.
    Tested
  • Keep checking the connection in a live dashboard
    Not shown working

How far pickfit got

Linux x86_64

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

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

Good for

  • pinpoint where a Wi-Fi connection dies and how to fix it
  • walk around to find Wi-Fi dead zones with live dashboard
  • diagnose a DNS-only outage
  • detect captive-portal login interception
  • output machine-readable diagnostics for scripts and CI

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 1 Nov 2026
  • Version 0.9.0

Differences the test machine hit

  • README: curl ... | sh installs wtfi and installed command is wtfi on PATH
    In the test: installer places binary in ~/.cargo/bin which is not on PATH in this box (PATH starts with ~/.local/bin); needed symlink to ~/.local/bin or PATH export
  • README: wtfi -w live dashboard with real-time latency sparklines
    In the test: when stdout is not a TTY (piped/timeout), wtfi -w falls back to one-shot text report instead of TUI; still shows header and topology

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.