pickfit

BrowseDeveloper CLIs

yottacode

Local-first terminal coding agent that turns issues into tested pull requests with approval gates.

Tested on Linux

Use it

Linux x86_64

You need first

  • Keys or accounts: OPENAI_API_KEY
  1. download install script from https://yottacode.ai/cli/install.sh

    curl -fsSL https://yottacode.ai/cli/install.sh -o /tmp/install.sh
  2. run install script with --no-modify-rc, installs 0.5.0 to ~/.yottacode/bin

    bash /tmp/install.sh --no-modify-rc

Check that it works

export PATH="$HOME/.yottacode/bin:$PATH" && yottacode --version

The output should contain “yottacode version 0.5.0”.

What it does

  • Turn issues into tested pull requests
    Not tested
  • Manage branches, commits and pull requests
    Not tested
  • Approve file writes and shell commands
    Not tested

How far pickfit got

Linux x86_64

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

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

Good for

  • review a PR diff, check CI and draft follow-up comment
  • reproduce failing test, patch code and rerun checks
  • update YAML, Helm, Terraform or deployment config
  • turn an issue into branch, commits and pull request
  • map an unfamiliar codebase in plan mode before editing

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 31 Oct 2026
  • Version 0.5.0

Differences the test machine hit

  • README: curl -fsSL https://yottacode.ai/cli/install.sh | bash installs yottacode ready to run
    In the test: installer puts binary in $HOME/.yottacode/bin which is not on default PATH (~/.local/bin); needed manual ln -sf ~/.yottacode/bin/yottacode ~/.local/bin/yottacode or export PATH
  • README: yottacode setup then yottacode
    In the test: both require a provider/API key (OPENAI_API_KEY etc) or Ollama; doctor exits 1 with 'no model set: pass --model <name>, export YOTTACODE_MODEL, or run yottacode setup'

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.