pickfit

BrowseDeveloper CLIs

m3 Memory

Local-first memory layer that stores facts and history for AI assistants to recall.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Python 3.12+
  1. Install m3-memory via uv tool

    uv tool install m3-memory

Check that it works

m3 --version

The output should contain “m3-memory 2026.10.25.0”.

First thing to try

m3 doctor 2>&1

Run m3 doctor first to check that the setup works.

What it does

  • Remember projects and preferences across sessions
    How to use it
    1. Save a memory with m3 memory memory_write --type decision --title "<title>" --content "<your text>".
    2. Look for the "Created:" line with the new memory's ID.
    Tested
  • Find memories without using the exact wording
    How to use it
    1. Ask in your own words with m3 memory memory_search --query "<your question>" --k 1.
    2. Read the matching memory in the "content" field of the result.
    Tested
  • Share one memory across AI assistants
    Not tested
  • Save and recall conversation history
    Not tested

How far pickfit got

Linux x86_64

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

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

Good for

  • remember facts from earlier sessions
  • recall past conversations
  • share memory across AI assistants
  • find memories by meaning
  • share notes and handoffs between agents

An alternative to Mem0, Letta and Zep.

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 2026.10.25.0

Differences the test machine hit

  • README: local BGE-M3 embedder provides semantic search
    In the test: m3 works via keyword fallback with EmbedFallbackError/EmbedPrimaryError warnings; no embedder setup needed for basic write/search
  • README: m3 doctor checks that everything is working
    In the test: m3 doctor exits 1 reporting warnings (no embedder, no agents, no LLM) but store and CLI remain usable
  • README: chat-log capture keeps conversations and finds them again
    In the test: conversation capture/recall uses m3 conversations conversation_start/conversation_append/conversation_search; m3 chatlog only has init/status/doctor/hook-path

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.