pickfit

BrowseDeveloper CLIs

openheim

Multi-provider LLM agent runtime with TUI, CLI, and ACP server.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Rust 1.91+
  • Keys or accounts: API key for at least one supported provider
  1. Download prebuilt Linux binary tarball

    curl -fSL https://github.com/weirdstuff-dev/openheim/releases/download/v0.17.1/openheim-v0.17.1-x86_64-unknown-linux-gnu.tar.gz -o /tmp/openheim.tar.gz
  2. Extract tarball and install binary to PATH

    mkdir -p /tmp/openheim-ex && tar -xzf /tmp/openheim.tar.gz -C /tmp/openheim-ex && mkdir -p ~/.local/bin && cp /tmp/openheim-ex/openheim ~/.local/bin/openheim && chmod +x ~/.local/bin/openheim

Check that it works

openheim --help

The output should contain “Usage: openheim”.

First thing to try

openheim init

Run openheim init first to set up the tool.

What it does

  • Run an agent loop that executes tools
    Not tested
  • Use different LLM providers
    Not tested
  • Run as a TUI, CLI, ACP agent or server
    Not tested
  • Connect external MCP servers and expose their tools
    Not tested

How far pickfit got

Linux x86_64

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

Good for

  • list files in the current directory
  • read, write and edit files via agent tools
  • search codebase and fetch web content
  • save and recall long-term memory notes
  • delegate tasks to subagents

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

Differences the test machine hit

  • README: cargo install openheim
    In the test: download prebuilt openheim-v0.17.1-x86_64-unknown-linux-gnu.tar.gz from GitHub releases and copy openheim binary to ~/.local/bin
  • README: --version or --help works (assumed --version exists)
    In the test: use openheim --help; openheim --version exits 2 with unexpected argument error
  • README: cargo build from source is auditable Rust code
    In the test: installed file is a precompiled binary tarball whose contents cannot be read/audited

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.