pickfit

BrowseDeveloper CLIs

Zeph

Memory-first AI agent with graph memory that runs locally or via cloud providers.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Rust>=1.98
  • Keys or accounts: provider API keys
  1. Download musl binary and checksum, verify

    mkdir -p /tmp/zd && cd /tmp/zd && curl -fsSL -O https://github.com/bug-ops/zeph/releases/download/v0.22.5/zeph-x86_64-unknown-linux-musl.tar.gz && curl -fsSL -O https://github.com/bug-ops/zeph/releases/download/v0.22.5/zeph-x86_64-unknown-linux-musl.tar.gz.sha256 && sha256sum -c zeph-x86_64-unknown-linux-musl.tar.gz.sha256
  2. Extract and install binary on PATH

    tar xzf /tmp/zd/zeph-x86_64-unknown-linux-musl.tar.gz -C /tmp/zd && chmod 0755 /tmp/zd/zeph && mkdir -p ~/.zeph/bin ~/.local/bin && mv /tmp/zd/zeph ~/.zeph/bin/zeph && ln -sf ~/.zeph/bin/zeph ~/.local/bin/zeph
Where the README and reality differ
  • README: curl -fsSL .../latest/download/install.sh | sh installs on Linux x86_64
    What worked: download zeph-x86_64-unknown-linux-musl.tar.gz + .sha256, verify, extract and symlink into ~/.local/bin

Check that it works

zeph --version

The output should contain “zeph 0.22.5”.

First thing to try

mkdir -p ~/.local/bin && ln -sf ~/.zeph/bin/zeph ~/.local/bin/zeph && export PATH="$HOME/.local/bin:$HOME/.zeph/bin:$PATH" && zeph doctor

Run zeph doctor first to check that your setup is ready.

What it does

  • Recall why past decisions were made
    Not shown working
  • Read files and run commands
    Not tested
  • Run long jobs with sub-agents
    Not tested
  • Send tasks to the cheapest capable provider
    Not shown working

How far pickfit got

Linux x86_64

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

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

Good for

  • code with full project context in a repo
  • deploy as team chat bot in Telegram Discord Slack
  • run privately 100% locally with Ollama
  • run long research loops and document RAG jobs
  • ingest documents into semantic memory

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

Differences the test machine hit

  • README: install.sh downloads and verifies zeph tarball
    In the test: install.sh fetches a prebuilt binary tarball which cannot be read as a script before running

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.