pickfit

BrowseDeveloper CLIs

Second Brain

Local knowledge vault CLI with hybrid search, entity graph, and MCP access to notes.

Tested on Linux

Use it

Linux x86_64

  1. install via uv tool install secondbrain-py

    uv tool install secondbrain-py
Where the README and reality differ
  • README: brain search "platform migration" --json --brief
    What worked: installed brain 0.3.0 has no --brief flag; `brain search` rejects it with `No such option: --brief (Possible options: --before)`

Check that it works

brain --version 2>&1

The output should contain “brain 0.3.0”.

First thing to try

brain doctor 2>&1

Run brain doctor first to check your setup.

What it does

  • Search notes with combined keyword and vector search
    Not tested
  • Explore the entity graph built from your notes
    Not tested
  • Enrich notes using a local LLM
    Not tested
  • Query your knowledge base through an MCP server
    Not tested

How far pickfit got

Linux x86_64

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

Good for

  • ingest a file into the knowledge base
  • hybrid search notes and transcripts
  • get a cited multi-hop answer from the corpus
  • generate a digest of newly landed notes
  • resurface older notes due for review

How pickfit tested it

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

Linux x86_64

Its main function works

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

Differences the test machine hit

  • README: brain demo needs only Docker; setup provisions Postgres container on 55432
    In the test: Docker Engine must be installed and running; box has no docker so `brain demo`, `brain setup` and DB-backed search cannot run

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.