pickfit

BrowseDeveloper CLIs

Xenon

Terminal AI coding agent that separates machine-verified results from items needing human check.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: python>=3.10
  • Keys or accounts: LLM API key
  1. Install Xenon from release wheel via pip

    pip install https://github.com/xianyu-sheng/Xenon/releases/download/v0.9.4/xenon_harness-0.9.4-py3-none-any.whl

Check that it works

xenon --version

The output should contain “xenon 0.9.4”.

First thing to try

xenon < /dev/null

Run xenon in your project folder to start the coding agent in the terminal.

What it does

  • Record tool runs in a hash-chained evidence log
    Not tested
  • Retry empty answers and list items to check by hand
    Not tested
  • Rewind and fork the conversation session tree
    Not tested
  • Require approval for actions outside the workspace
    Not tested

How far pickfit got

Linux x86_64

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

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

Good for

An alternative to Aider, Claude Code, OpenCode and Crush.

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

Differences the test machine hit

  • README: `xenon` starts the session directly.
    In the test: Pipe EOF via `xenon < /dev/null` so the REPL sees end-of-input and exits 0 with banner plus API-key hint; a plain interactive `xenon` waits for input and had to be killed after 20s.

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.