pickfit

BrowseDeveloper CLIs

Alysis Code

Open-source multi-model agent for coding, research, and everyday terminal workflows.

Tested on Linux and Windows

Use it

Linux x86_64

You need first

  • Runtimes: Python 3.11+
  • Keys or accounts: Provider API key from OpenAI, Anthropic, DeepSeek, Gemini, OpenRouter and more
  1. pipx install alysis-code

    pipx install alysis-code

Check that it works

alysis --version 2>&1

The output should contain “0.15.2”.

First thing to try

alysis sandbox doctor --smoke 2>&1

Run alysis sandbox doctor --smoke to check that the tool is set up correctly.

Windows x86_64

You need first

  • Runtimes: Python 3.11+
  • Keys or accounts: Provider API key from OpenAI, Anthropic, DeepSeek, Gemini, OpenRouter and more
  1. pipx install alysis-code

    pipx install alysis-code

Check that it works

$env:Path = [Environment]::GetEnvironmentVariable('Path','Machine') + ';' + [Environment]::GetEnvironmentVariable('Path','User'); alysis --version

The output should contain “0.15.2”.

First thing to try

alysis sandbox doctor --smoke

Run alysis sandbox doctor --smoke to check that the tool is set up correctly.

What it does

  • Run coding, research and everyday workflows
    Not shown working
  • Use multiple model providers and local models
    Not shown working
  • Run commands in an isolated sandbox
    Not shown working
  • Turn plans into verified changes
    Not shown working

How far pickfit got

Linux x86_64

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

Windows x86_64

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

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

Good for

  • Fix failing tests in a project
  • Summarize folder notes into a project brief
  • Research a question with built-in web search
  • Execute planned tasks with verification

An alternative to Claude Code, Codex CLI, OpenCode, Command Code and Kilo Code.

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

Differences the test machine hit

  • README: curl install.sh provisions uv and Python 3.12 when needed
    In the test: pipx install alysis-code worked directly on Python 3.12; no uv/Python bootstrap needed

Windows x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 31 Oct 2026
  • Version 0.15.2

Differences the test machine hit

  • README: alysis sandbox doctor --smoke checks sandbox
    In the test: exits 1 with 'Status: not ready' when Docker Desktop not installed; needs Docker to provide backend
  • README: (Windows steps)
    In the test: pickfit ran these steps in PowerShell 7 (pwsh 7.6.9) as a standard user; the built-in Windows PowerShell 5.1 is not verified and does not run `&&`.
  • README: (Windows steps)
    In the test: On Windows, open a new terminal after installing so PATH includes the tool; the sandbox refreshed PATH in the same session instead.

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.