pickfit

BrowseDeveloper CLIs

Martty

Terminal UI ACP client to run and observe AI agents via DSH or other harnesses.

Tested on Linux and WindowsKnown vulnerabilities

Use it

Before you install: known vulnerabilities

pickfit found 4 known high or critical vulnerabilities in the packages a fresh install brings (OSV.dev, 3 Nov 2026). Weigh this before you install it.

  • npm:undici 6.29.0 undici vulnerable to TLS certificate validation bypass via dropped tls options in Agent (GHSA-2m5v-pch6-74hx, high, fixed in 6.29.1)
  • npm:zod 4.4.3 Zod can exhaust memory while validating oversized constrained collections (GHSA-mrhx-c7xc-m3w5, high, fixed in 4.6.6)
See 2 more

Linux x86_64

You need first

  • Runtimes: Node.js 22.19+
  1. Install martty globally via npm

    npm install --global martty

Check that it works

which martty-cli; ls -la ~/.local/bin/martty* ; martty-cli --help

The output should contain “martty — terminal-native ACP client UI”.

First thing to try

martty-cli --dump-frame

Run martty in a terminal to open the interface with a prompt asking what you want to build.

Windows x86_64

You need first

  • Runtimes: Node.js 22.19+
  1. npm install --global martty

    npm install --global martty
Where the README and reality differ
  • README: npm install --global martty then martty --demo
    What worked: package only installs martty-cli bin; first launch via martty-cli creates martty shim - martty command was still not found after multiple martty-cli runs in this session

Check that it works

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

The output should contain “martty 0.3.3”.

First thing to try

$env:Path = [Environment]::GetEnvironmentVariable('Path','Machine') + ';' + [Environment]::GetEnvironmentVariable('Path','User'); martty-cli harness list 2>&1

Run martty in a terminal to open the interface with a prompt asking what you want to build.

What it does

  • Watch agent work in the terminal
    Not shown working
  • Connect DSH and other ACP agents
    Not shown working
  • Queue messages and steer the agent
    Not tested
  • Build the interface from Cordis plugins
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 1 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

  • view streaming agent replies, reasoning and tool calls in terminal
  • select model and agent preset
  • switch harness and start a new session

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

Differences the test machine hit

  • README: npm install --global martty then run martty
    In the test: global install provides martty-cli only; martty shim auto-created on first martty-cli run
  • README: martty --demo and martty --demo-skin to see the UI
    In the test: headless box has no TTY for interactive TUI; martty --dump-frame (and --dump-frame --demo-skin) renders one demo frame as text and exits 0

Windows x86_64

Its main function works

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

Differences the test machine hit

  • README: martty --dump-frame renders one frame
    In the test: martty-cli --dump-frame does render frame (tool calls, thought, composer) but then exits with error: martty exited before connecting (code=0) and exit code 1
  • 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.