pickfit

BrowseDeveloper CLIs

PRAANA

Terminal coding agent that curates model context each turn and reuses learnings across sessions.

Tested on macOS and LinuxKnown vulnerabilities

Use it

Before you install: known vulnerabilities

pickfit found 5 known high or critical vulnerabilities in the packages a fresh install brings (OSV.dev, 3 Nov 2026). Weigh this before you install it.

  • npm:seroval 1.5.6 Seroval: `fromJSON()` Promise thenable assimilation invokes plugin-produced callables (bypass of GHSA-mv8w-475r-vwqw) (GHSA-p6vx-979v-rg4c, critical, fixed in 1.6.2)
See 4 more

macOS arm64

You need first

  • Runtimes: Bun>=1.4
  • Keys or accounts: ANTHROPIC_API_KEY, OPENAI_API_KEY
  1. download install.sh from GitHub

    curl -fsSL https://raw.githubusercontent.com/amitkumardubey/praana/main/install.sh -o /tmp/praana-install.sh && wc -l /tmp/praana-install.sh && head -n 200 /tmp/praana-install.sh
  2. run install.sh to install praana binary to ~/.local/bin

    bash /tmp/praana-install.sh

Check that it works

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

The output should contain “PRAANA v0.16.0”.

Run praana in your project directory to start a coding session in the terminal.

Linux x86_64

You need first

  • Runtimes: Bun>=1.4
  • Keys or accounts: ANTHROPIC_API_KEY, OPENAI_API_KEY
  1. download install.sh for reading

    curl -fsSL https://raw.githubusercontent.com/amitkumardubey/praana/main/install.sh -o /tmp/install.sh
  2. install praana via install.sh

    bash /tmp/install.sh

Check that it works

praana --version

The output should contain “PRAANA v0.16.0”.

First thing to try

praana doctor

Run praana in your project directory to start a coding session in the terminal.

What it does

  • Run long coding sessions in the terminal
    Not tested
  • Curate the prompt context on every turn
    Not shown working
  • Keep learnings across sessions on your machine
    Not shown working
  • Resume sessions by replaying checkpoints
    Not shown working

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

  • end session and extract learnings with summariser
  • search cross-session memory with recall query
  • show ranked memory digest for project

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

Differences the test machine hit

  • README: praana doctor checks config + provider keys (implied success)
    In the test: doctor exits 1 when no provider configured, but still reports ✓ native and ✓ search; this is expected without ANTHROPIC_API_KEY

Linux x86_64

Its main function works

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

Differences the test machine hit

  • README: curl -fsSL .../install.sh | bash installs praana into ~/.local/bin
    In the test: no extra step; ~/.local/bin is already first on PATH and install verified SHA256 and smoked --version by itself
  • README: Status v0.15.1
    In the test: installed PRAANA v0.16.0; README badge still says v0.15.1

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.