pickfit

BrowseDeveloper CLIs

hako-code

Single-file C terminal coding agent for local and cloud models with gated tools.

Tested on macOS and Linux

Use it

macOS arm64

You need first

  • System packages: curl
  1. download hako.sh proxy

    curl -fsSL https://mithraeums.github.io/hako.sh -o /tmp/hako.sh && ls -lh /tmp/hako.sh && wc -l /tmp/hako.sh
  2. download real install.sh

    curl -fsSL "https://raw.githubusercontent.com/mithraeums/hako-code/main/install.sh" -o /tmp/install.sh && ls -lh /tmp/install.sh && wc -l /tmp/install.sh
  3. install hako to ~/.local/bin

    sh /tmp/install.sh && ls -lh ~/.local/bin/hako && ~/.local/bin/hako --version

Check that it works

hako --version

The output should contain “hako v0.3.0 (build Oct 30 2026”.

First thing to try

hako -p "summarize README.md" --output-format json

Run hako -p "summarize README.md" --output-format json in a project folder to give the agent a one-off task.

Linux x86_64

You need first

  • System packages: curl
  1. Download installer proxy only

    curl -fsSL https://mithraeums.github.io/hako.sh -o /tmp/hako.sh
  2. Download real installer script

    curl -fsSL https://raw.githubusercontent.com/mithraeums/hako-code/main/install.sh -o /tmp/hako-install.sh
  3. Install hako via vetted script

    sh /tmp/hako-install.sh

Check that it works

hako --help

The output should contain “usage: hako [options]”.

First thing to try

hako --serve --port 8787 --no-color
curl -sS http://127.0.0.1:8787/api/models

Run hako -p "summarize README.md" --output-format json in a project folder to give the agent a one-off task.

What it does

  • Run a coding agent in the terminal
    Not tested
  • Use local models or cloud providers
    Not shown working
  • Read and edit files and run shell commands
    Not tested
  • Keep sessions and use skills
    Not tested

How far pickfit got

macOS arm64

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

Linux x86_64

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

Good for

  • list files in a directory
  • summarize README.md
  • score tool-call reliability with bench

An alternative to Hermes and Claude Code.

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
  • Version v0.3.0

Differences the test machine hit

  • README: curl -fsSL https://mithraeums.github.io/hako.sh | sh
    In the test: hako.sh is a 4-line proxy that execs curl for https://raw.githubusercontent.com/mithraeums/hako-code/main/install.sh; downloaded both scripts and read before executing
  • README: hako --update pulls latest release
    In the test: hako --update failed with 'could not fetch latest release' (transient GitHub API limit) even though install had just fetched v0.3.0
  • README: install drops hako into /usr/local/bin (or ~/.local/bin)
    In the test: on this unprivileged box it correctly chose ~/.local/bin/hako which is on PATH

Linux x86_64

Its service answers requests

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version v0.3.0

Differences the test machine hit

  • README: curl -fsSL https://mithraeums.github.io/hako.sh | sh
    In the test: downloaded proxy and real installer, read both, then ran local file; installer fetched a prebuilt binary tarball verified by sha256 which cannot be read as text
  • README: README badge shows v0.2.9
    In the test: installed v0.3.0 reported as hako v0.3.0
  • README: README documents :providers/:models/:sessions interactive commands
    In the test: used hako --serve API paths /api/models and /api/sessions found by scanning binary; --help and README do not document them

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.