pickfit

BrowseDeveloper CLIs

lcode

Local terminal coding agent that explores repos, edits files, and runs commands.

Tested on macOS and Linux

Use it

macOS arm64

You need first

  • A GPU is optional
  1. brew install nasser1941/tap/lcode

    brew install nasser1941/tap/lcode

Check that it works

lcode --help 2>&1

The output should contain “usage: lcode”.

First thing to try

lcode models 2>&1

Run lcode models first to see which local models are available.

Linux x86_64

You need first

  • A GPU is optional
  1. Install lcode via uv tool install lcode-cli

    uv tool install lcode-cli

Check that it works

lcode --help 2>&1

The output should contain “A local-first terminal coding agent”.

First thing to try

lcode models 2>&1

Run lcode models first to see which local models are available.

What it does

  • Run fully on your machine with open-weight models
    Not shown working
  • Chat with your repository in the terminal
    Not tested
  • Write and edit files
    Not tested
  • Run scripts and tests
    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

  • answer questions about how code works with file references
  • write scripts and run them in the repo
  • find failing tests and fix them
  • search code semantically for specific behavior
  • review repository changes with findings

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 0.53.0

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version 0.52.0

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.