pickfit

BrowseDeveloper CLIs

Uteke

Local-first memory engine that stores, recalls, and searches memories for AI agents offline.

Tested on Linux

Use it

Linux x86_64

  1. Download install script only

    curl -sSL codecora.dev/uteke/install -o /tmp/uteke-install.sh
  2. Install uteke via script

    sh /tmp/uteke-install.sh
Where the README and reality differ
  • README: uteke recall "caching decision" --room engineering
    What worked: uteke room recall engineering "caching decision" (room recall subcommand)
  • README: uteke room create "engineering" --description "Team decisions"
    What worked: uteke room create engineering (no --description flag)
  • README: uteke recall "deploy" --at 2025-01-15
    What worked: RFC3339 timestamp e.g. uteke recall "q" --at 2030-01-01T00:00:00Z

Check that it works

uteke --version

The output should contain “uteke 0.22.1”.

First thing to try

uteke room create smoke-room && uteke remember "We chose Redis for caching over Memcached" --room smoke-room --author alice && uteke remember "Redis cluster: 3 nodes, 2 replicas each" --room smoke-room --author bob
uteke room recall smoke-room "caching decision"

Run uteke remember "<your text>" to store your first memory.

What it does

  • Share memories across agents in rooms
    How to use it
    1. Create a room with uteke room create <room>.
    2. Add memories to it with uteke remember "<your text>" --room <room> --author <name>.
    3. Search the room with uteke room recall <room> "<query>".
    Tested
  • Recall memories as of a point in time
    How to use it
    1. Store a memory with uteke remember "<your text>".
    2. Recall it as of a given time with uteke recall "<query>" --at <timestamp>.
    Tested
  • Search memories by meaning and keywords
    Not tested

How far pickfit got

Linux x86_64

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

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

Good for

  • store a memory from the command line
  • recall memories by meaning and keyword
  • share memories across agents in rooms

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

Differences the test machine hit

  • README: curl -sSL codecora.dev/uteke/install | sh
    In the test: Download to /tmp/uteke-install.sh first, read it, then run sh /tmp/uteke-install.sh

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.