pickfit

BrowseDeveloper CLIs

goatedcontext

Gives coding agents persistent local memory of developer preferences across sessions.

Tested on macOS and LinuxKnown vulnerabilities

Use it

Before you install: known vulnerabilities

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

  • npm:zod 3.25.76 Zod can exhaust memory while validating oversized constrained collections (GHSA-mrhx-c7xc-m3w5, high, fixed in 4.6.6)

macOS arm64

You need first

  • Runtimes: Node 22.13+
  1. install ctx via npx goatedcontext setup

    npx goatedcontext setup
Where the README and reality differ
  • README: ctx remember --scope repo --always "..." works anywhere
    What worked: repo scope requires git repo; fails with 'Not inside a git repository' outside one, need git init or --scope global

Check that it works

ctx --version 2>&1

The output should contain “0.4.4”.

First thing to try

ctx agents 2>&1

Run ctx agents inside a project folder to get started.

Linux x86_64

You need first

  • Runtimes: Node 22.13+
  1. install goatedcontext via npx goatedcontext setup

    npx goatedcontext setup

Check that it works

ctx --version

The output should contain “0.4.4”.

First thing to try

ctx agents

Run ctx agents inside a project folder to get started.

What it does

  • Save your working preferences for coding agents
    How to use it
    1. Open a terminal in your git repository.
    2. Run ctx remember --scope repo --always "<your preference>" to save a preference for that repository.
    Tested
  • Get saved preferences back in later sessions
    How to use it
    1. Run ctx prefs to list your saved preferences.
    2. In your repository, run ctx agent context --task "<your task>" --json to get the preferences that apply to a task.
    Tested
  • Browse saved preferences in a terminal UI
    Not tested

How far pickfit got

macOS arm64

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

Linux x86_64

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

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

Good for

  • Save developer working preferences locally for reuse
  • Retrieve saved preferences in fresh sessions
  • Browse stored preferences and proposals in terminal UI

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 0.4.4

Differences the test machine hit

  • README: ctx doctor should succeed
    In the test: ctx doctor exits 1 with warnings when native agents not installed (expected diagnostics, not failure)
  • README: ctx with no args opens interactive browser
    In the test: in non-interactive/CI it prints help and never emits terminal codes (as documented)

Linux x86_64

Its main function works

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

Differences the test machine hit

  • README: ctx doctor diagnostics
    In the test: ctx doctor exits 1 when integrations missing (3 problem(s), 2 warning(s)) — not 0; still indicates success
  • README: Run ctx with no arguments to open interactive memory browser
    In the test: In non-interactive/CI ctx prints help and exits 1 instead of opening TUI, as README notes later

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.