pickfit

BrowseDeveloper CLIs

memcode

Terminal coding agent that keeps persistent repo memory and runs as self-hosted chat gateway.

Tested on Linux

Use it

Linux x86_64

You need first

  • Keys or accounts: OPENAI_API_KEY, ANTHROPIC_API_KEY
  1. Download install script for reading before running

    curl -fsSL https://memcode.ai/install.sh -o /tmp/memcode-install.sh
  2. Install memcode via downloaded script with bash

    bash /tmp/memcode-install.sh

Check that it works

memcode --help

The output should contain “Available Commands:”.

First thing to try

memcode doctor

Run memcode doctor first to check that the tool is set up correctly.

What it does

  • Run an interactive coding agent in your repo
    Not tested
  • Remember repo layout, history and preferences
    Not shown working
  • Run tasks from chat channels
    Not tested
  • Run agents on their own on a schedule
    Not shown working

How far pickfit got

Linux x86_64

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

Good for

  • pick up where you left off last week in a repo
  • fix a bug from Telegram
  • draft a plan for codebase change for approval
  • keep dependencies current and triage security advisories
  • send a voice note to the agent

An alternative to Hermes and OpenClaw.

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

Differences the test machine hit

  • README: curl -fsSL https://memcode.ai/install.sh | sh
    In the test: run the downloaded script with `bash /tmp/memcode-install.sh` for exit 0; `sh` (dash) still installed the binary to ~/.local/bin but exited 2 after install with no controlling terminal
  • README: install script verifies checksum before installing
    In the test: installer downloads memcode_Linux_x86_64.tar.gz binary archive plus checksums.txt from memcode.ai/dl (GitHub Releases) and installs unverified binary beyond checksum

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.