pickfit

BrowseDeveloper CLIs

Apexo

Open-source coding agent with terminal, web and desktop interfaces on a shared local runtime.

Tested on macOS and Linux

Use it

macOS arm64

You need first

  • Needs the network
  1. Install apexo-code via npm -g

    npm install -g apexo-code
    

Check that it works

apexo --version

The output should contain “1.1.0”.

First thing to try

apexo auth list

Run apexo auth list to see which accounts and providers are set up.

Linux x86_64

You need first

  • Needs the network
  1. Install apexo via npm candidate 1

    npm install -g apexo-code

Check that it works

apexo --version

The output should contain “1.1.0”.

First thing to try

apexo auth list

Run apexo auth list to see which accounts and providers are set up.

What it does

  • Set a goal and let the agent work until it is verified
    Not tested
  • Run structured workflows across several sessions
    Not tested
  • Manage background tasks and subagents
    Not tested
  • Review and organize saved project memory
    Not tested

How far pickfit got

macOS arm64

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

Linux x86_64

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

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

Good for

  • Define autonomous goal and iterate until verified
  • Run structured multi-step workflows in child sessions
  • Manage background shell commands and scheduled jobs
  • Review and consolidate persistent project memory
  • Run shell commands under OS-level sandboxing

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

macOS arm64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 1 Nov 2026
  • Version 1.1.0

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version 1.1.0

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.