pickfit

BrowseDeveloper CLIs

urga

Terminal UI for HashiCorp Nomad to browse and manage jobs, allocations, clients, and other resources.

Tested on Linux

Use it

Linux x86_64

You need first

  • Needs the network
  • Keys or accounts: NOMAD_TOKEN
  1. download linux_amd64 tarball from GitHub releases and install to ~/.local/bin

    cd /tmp && curl -fL -o urga.tar.gz https://github.com/ingvarch/urga/releases/download/v0.16.0/urga_0.16.0_linux_amd64.tar.gz && mkdir -p ~/.local/bin && tar xzf urga.tar.gz -C /tmp && cp /tmp/urga ~/.local/bin/urga && chmod +x ~/.local/bin/urga && ~/.local/bin/urga --help

Check that it works

urga -version

The output should contain “urga v0.16.0”.

Run urga in a terminal to open the Nomad terminal UI.

What it does

  • List jobs, allocations and cluster resources
    Not tested
  • Watch job deployments as they happen
    Not tested
  • View and follow task logs and files
    Not tested
  • Start, stop, scale and restart jobs
    Not tested

How far pickfit got

Linux x86_64

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

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

Good for

  • list jobs and allocations
  • show task logs and allocation files
  • edit a job and preview plan before submit
  • create, edit and delete namespaces
  • manage ACL tokens, policies, roles and auth methods

How pickfit tested it

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

Linux x86_64

Installs and starts

  • Replayed from scratch
  • Works offline
  • Checked on 1 Nov 2026
  • Version v0.16.0

Differences the test machine hit

  • README: go install github.com/ingvarch/urga/cmd/urga@latest
    In the test: requires Go toolchain not present in box; used pre-built linux_amd64 tarball instead
  • README: sudo apt install ./urga_*_amd64.deb / sudo dnf / yay -S urga
    In the test: no sudo/root or AUR available; extracting tarball to ~/.local/bin works without root
  • README: README implies binary archive install is alternative
    In the test: tarball contains single binary 'urga' plus LICENSE/README; direct copy to ~/.local/bin works

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.