pickfit

BrowseDeveloper CLIs

model-orchestrator

Routes coding-agent tasks to cheaper or stronger models using editable rules, subagents, and a CLI runner.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: node>=18
  1. Global npm install of model-orchestrator

    npm install -g model-orchestrator

Check that it works

aunx --help

The output should contain “aunx route [--dir PATH]”.

First thing to try

npx model-orchestrator --list

Run aunx route "<your task>" to get a routing suggestion for a task.

What it does

  • Route routine work to cheaper models
    How to use it
    1. Run aunx route "<your task>" with a routine task such as a rename.
    2. Read the suggestion line for the lane, model tier and effort level.
    Tested
  • Get a suggested lane for a task
    How to use it
    1. Run aunx route "<your task>".
    2. Check the output for the suggested lane, model tier and effort.
    Tested
  • Hand off scoped work to worker lanes
    Not shown working
  • See your routing split and subagent activity
    Not shown working

How far pickfit got

Linux x86_64

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

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

Good for

  • route routine coding work to cheaper models
  • delegate scoped work to another AI CLI lane via brief
  • get a model routing suggestion for a task
  • summarize local routing split and subagent activity
  • run acceptance checks against delegated work

An alternative to LiteLLM, Portkey, OpenRouter and claude-code-router.

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 1.1.2

Differences the test machine hit

  • README: aunx cli-run --doctor
    In the test: Exits 10 listing 6 enabled lanes with binaries MISSING when no project lanes are installed; still the correct honest doctor output.

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.