pickfit

BrowseDeveloper CLIs

Nedster

Local coding agent that runs read-edit-test loops via Ollama and returns JSON results.

Tested on macOS and Linux

Use it

macOS arm64

You need first

  • Runtimes: python>=3.11
  • A GPU is optional
  • At least 8 GB of RAM
  1. git clone Nedster to obtain install.sh

    git clone https://github.com/unrealumanga/Nedster.git /tmp/Nedster 2>&1 && ls /tmp/Nedster/install.sh 2>&1 && wc -l /tmp/Nedster/install.sh
  2. uv tool install --force /tmp/Nedster (core of install.sh, clean without sudo)

    uv tool install --force /tmp/Nedster

Check that it works

nedster --version

The output should contain “Nedster 4.0.0a1”.

Linux x86_64

You need first

  • Runtimes: python>=3.11
  • A GPU is optional
  • At least 8 GB of RAM
  1. Download Nedster source with installer script

    git clone https://github.com/unrealumanga/Nedster.git /tmp/Nedster2
  2. Install nedster via installer payload (uv tool install, same as install.sh)

    uv tool install --force /tmp/Nedster2

Check that it works

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

The output should contain “Nedster 4.0.0a1”.

First thing to try

export PATH="$HOME/.local/bin:$PATH" && nedster doctor

What it does

  • Run a read, edit and test loop on your machine
    Not tested
  • Get JSON results backed by test runs
    Not tested
  • Chat with the agent in a terminal coding interface
    Not tested

How far pickfit got

macOS arm64

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

Linux x86_64

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

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

Good for

  • fix bugs with a known location or traceback
  • implement 1-3 file features with tests
  • perform multi-file renames
  • write tests for existing code
  • answer where-is and how-does-it-flow code questions

An alternative to Claude Code and Codex.

How pickfit tested it

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

macOS arm64

Installs and starts

  • Replayed from scratch
  • Works offline
  • Checked on 1 Nov 2026
  • Version 4.0.0a1

Differences the test machine hit

  • README: ./install.sh installs nedster and runs nedster setup (brew install --cask ollama-app)
    In the test: install.sh fails on standard non-admin user: brew cask needs sudo for /Applications; install succeeds via uv tool install but setup must be skipped

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version Nedster 4.0.0a1

Differences the test machine hit

  • README: ./install.sh installs nedster and runs nedster setup to ready state
    In the test: uv tool install portion succeeds and provides nedster; nedster setup aborts because the bundled Ollama installer requires root and no Ollama server/model exists on the 2GB CPU-only box
  • README: nedster opens the TUI: chat
    In the test: bare nedster with stdin closed and no TTY printed argparse usage (exit 0) instead of opening the full-screen TUI

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.