pickfit

BrowseDeveloper CLIs

FLASH CLI

Local-first agent shell that chats with Ollama models via CLI and web UI with tools.

Tested on macOS and Linux

Use it

macOS arm64

  1. git clone Flash repo to get requirements.txt

    git clone https://github.com/Natuworkguy/Flash /tmp/flash-repo && ls /tmp/flash-repo && cat /tmp/flash-repo/requirements.txt
  2. pip3 install --break-system-packages -r requirements.txt

    pip3 install --break-system-packages -r /tmp/flash-repo/requirements.txt && pip3 show ollama
  3. pip3 install --break-system-packages -e . to install flash package

    pip3 install --break-system-packages -e /tmp/flash-repo && flash --help; echo HELP_EXIT:$?
    flash --version
Where the README and reality differ
  • README: pip install -r requirements.txt installs Flash
    What worked: requirements.txt only installs dependencies; need pip install -e . to provide `flash` entry point

Check that it works

flash --version

The output should contain “Flash CLI v0.5.12”.

First thing to try

printf "/bye\n" | flash

Run flash to start a chat session in the terminal, and type /bye to exit.

Linux x86_64

  1. Clone repo for pip install

    git clone https://github.com/Natuworkguy/Flash flash-src
  2. Install deps via pip candidate 1

    python3 -m pip install -r flash-src/requirements.txt
  3. Install flash package so flash is on PATH

    python3 -m pip install ./flash-src && flash --version

Check that it works

flash --version

The output should contain “Flash CLI v0.5.12”.

First thing to try

flash --extension-list

Run flash to start a chat session in the terminal, and type /bye to exit.

What it does

  • Chat with local models in the terminal
    Not tested
  • Run shell commands through the AI
    Not tested
  • Build 3D models from prompts
    Not tested
  • Talk to Flash by voice
    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

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

Good for

  • chat with local Ollama models from the terminal
  • execute shell commands with ! prefix
  • send a local image to a vision model

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.5.12

Differences the test machine hit

  • README: pip install -r requirements.txt
    In the test: pip3 install --break-system-packages -r requirements.txt (Homebrew Python is externally-managed, PEP 668)

Linux x86_64

Its main function works

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

Differences the test machine hit

  • README: pip install -r requirements.txt then python3 run.py
    In the test: also run pip install ./flash-src to provide flash on PATH; requirements.txt alone only enables python3 run.py

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.