pickfit

BrowseDeveloper CLIs

loci

Shared local knowledge base with hybrid search, cited Q&A and MCP access for AI coding tools.

Tested on LinuxKnown vulnerabilities

Use it

Before you install: known vulnerabilities

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

  • pypi:chromadb 1.5.9 ChromaDB has a code injection vulnerability (GHSA-36p7-vc44-83pf, critical, no fix yet)
See 3 more

Linux x86_64

You need first

  • Runtimes: Python 3.11+
  • Keys or accounts: BRAIN_LLM_API_KEY, BRAIN_EMBED_API_KEY
  1. install loci via uv tool

    uv tool install loci-rag

Check that it works

loci --version 2>&1

The output should contain “loci 0.9.0”.

First thing to try

loci demo 2>&1

Run loci demo to see a sample search over example notes.

What it does

  • Search across your notes
    How to use it
    1. Run loci demo to try a search on sample notes.
    2. Read the ranked results, each showing the file and section that matched.
    Tested
  • Ask questions and get answers with citations
    Not shown working
  • Find what AI coding agents remember
    Not tested
  • Manage the knowledge base in a web console
    Not tested

How far pickfit got

Linux x86_64

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

Good for

  • find a decision buried in notes
  • ask a question and check cited evidence
  • share context between AI tools
  • inspect what each coding agent remembers
  • manage knowledge base in web console

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

Differences the test machine hit

  • README: loci search / ask / serve-http examples with no mention of required keys in quick-start snippet
    In the test: loci demo works with no config, key or network; loci search/ask/serve-http exit 1 demanding config.toml sources plus BRAIN_LLM_API_KEY and BRAIN_EMBED_API_KEY

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.