pickfit

BrowseDeveloper CLIs

OpenCode Swarm

Architect-led OpenCode plugin that plans, codes, reviews and tests via specialized agents.

Tested on LinuxKnown vulnerabilities

Use it

Before you install: known vulnerabilities

pickfit found 5 known high or critical vulnerabilities (6 findings, one per affected package version) in the packages a fresh install brings (OSV.dev, 3 Nov 2026). Weigh this before you install it.

  • npm:toml 4.3.0 toml-node: Quadratic-complexity DoS via many array-of-tables headers in toml.parse() (GHSA-4qx8-w7c3-pj3p, high, fixed in 5.0.1)
  • npm:zod 4.1.8 Zod can exhaust memory while validating oversized constrained collections (GHSA-mrhx-c7xc-m3w5, high, fixed in 4.6.6)
See 4 more

Linux x86_64

You need first

  • Runtimes: Bun >= 1.3.13, Node.js >= 22.13
  1. download bun installer

    curl -fsSL https://bun.sh/install -o /tmp/bun-install.sh
  2. install bun to ~/.bun/bin

    bash /tmp/bun-install.sh
  3. npm install -g opencode-swarm

    npm install -g opencode-swarm
  4. run opencode-swarm install to register plugin

    export PATH="$HOME/.bun/bin:$PATH" && opencode-swarm install
Where the README and reality differ
  • README: npm install requires Node.js >=22.13 and uses node:sqlite sidecar
    What worked: npm-installed binary is a bun shim (env: 'bun': No such file or directory) and still requires Bun >=1.3.13 in PATH; installed Bun via official install script and prepended ~/.bun/bin to PATH

Check that it works

export PATH="$HOME/.bun/bin:$HOME/.local/bin:$PATH" && opencode-swarm --version

The output should contain “opencode-swarm 7.200.17”.

First thing to try

export PATH="$HOME/.bun/bin:$PATH" && opencode-swarm run guardrail explain "rm -rf /etc/passwd" 2>&1
echo "---"
export PATH="$HOME/.bun/bin:$PATH" && opencode-swarm run preflight 2>&1

What it does

  • Coordinate specialized architect-led agent team
    Not tested
  • Enforce gated reviewer and test approval
    Not tested
  • Run security, secrets and dependency scans
    Not shown working
  • Save and resume sessions in .swarm
    Not tested

How far pickfit got

Linux x86_64

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

Good for

An alternative to oh-my-opencode (now OmO) and get-shit-done (now GSD Core).

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 2 Nov 2026
  • Version 7.200.17

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.