pickfit

BrowseDeveloper CLIs

Switchya & Switchyard Gateway

Local workspace and Rust gateway that routes OpenAI, Anthropic and Gemini requests to chosen providers.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Rust 1.88+
  • Keys or accounts: OpenAI, Anthropic or Gemini API key
  1. Download Linux x64 binary and install to PATH

    rm -f ~/.local/bin/switchyard && curl -sL -o /tmp/swyd.tar.gz https://github.com/ichikuruma22-star/switchyard/releases/download/v0.1.2/switchyard-0.1.2-x86_64-unknown-linux-gnu.tar.gz && mkdir -p ~/.local/bin && tar xzf /tmp/swyd.tar.gz -C /tmp && cp /tmp/switchyard-0.1.2-x86_64-unknown-linux-gnu/switchyard ~/.local/bin/switchyard && chmod +x ~/.local/bin/switchyard

Check that it works

switchyard version

The output should contain “switchyard 0.1.2”.

First thing to try

switchyard version

Run switchyard version to confirm the gateway is installed.

What it does

These come from the README; pickfit didn’t check them one by one.

  • Translate requests between LLM API formats
    Not tested
  • Route requests to the providers you choose
    Not tested
  • Send coding tasks and review proposed edits
    Not tested
  • Watch request traffic in the built-in dashboard
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. Produces output
  4. Works offline

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

Good for

  • Serve OpenAI Chat Completions requests via Anthropic
  • Serve Anthropic Messages requests via OpenAI
  • Serve Gemini generateContent requests via any provider
  • Send coding task and review proposed edits and commands
  • Monitor requests and provider health in dashboard

An alternative to CLIProxyAPI.

How pickfit tested it

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

Linux x86_64

It produces model output

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

Differences the test machine hit

  • README: cargo install --git https://github.com/ichikuruma22-star/switchyard switchyard and cargo build --release -p switchyard (Rust 1.88+)
    In the test: Downloaded prebuilt Linux x86_64 glibc binary tarball switchyard-0.1.2-x86_64-unknown-linux-gnu.tar.gz from GitHub releases v0.1.2 and copied inner switchyard binary to ~/.local/bin, as documented in README Quick start alternative to cargo

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.