pickfit

BrowseDeveloper CLIs

BugBuster Code

Model-agnostic terminal AI coding agent with tools for reading, editing, and running code.

Tested on Linux

Use it

Linux x86_64

You need first

  • Keys or accounts: OPENAI_API_KEY, ANTHROPIC_API_KEY

These steps ran from a folder named work in the home folder, which already existed. Make it and run them from there:

mkdir -p "$HOME/work" && cd "$HOME/work"
  1. download correct linux asset

    curl -sL -o /tmp/bugbuster-code.tar.gz https://github.com/Cavibora/bugbuster-code/releases/download/v1.3.0/bugbuster-code_1.3.0_linux_x86_64.tar.gz
  2. extract and install binary to local bin

    mkdir -p ~/.local/bin && tar xzf /tmp/bugbuster-code.tar.gz -C /tmp && mv /tmp/bugbuster ~/.local/bin/bugbuster && chmod +x ~/.local/bin/bugbuster
Where the README and reality differ
  • README: curl -sL https://github.com/Cavibora/bugbuster-code/releases/latest/download/bugbuster_$(uname -s)_$(uname -m).tar.gz | tar xz returns 'Not Found' (no such asset)
    What worked: Query GitHub API for release assets and download https://github.com/Cavibora/bugbuster-code/releases/download/v1.3.0/bugbuster-code_1.3.0_linux_x86_64.tar.gz (lowercase os/arch, versioned, with -code prefix)
Verified in pickfit: the commands exactly as its sandbox ran them

For the record only: they name the sandbox's home, /home/sbx.

curl -sL -o /tmp/bugbuster-code.tar.gz https://github.com/Cavibora/bugbuster-code/releases/download/v1.3.0/bugbuster-code_1.3.0_linux_x86_64.tar.gz
mkdir -p ~/.local/bin && tar xzf /tmp/bugbuster-code.tar.gz -C /tmp && mv /tmp/bugbuster ~/.local/bin/bugbuster && chmod +x ~/.local/bin/bugbuster
bugbuster --version
rm -f /home/sbx/work/bugbuster.yaml /home/sbx/.bugbuster/config.yaml
bugbuster config init

Check that it works

bugbuster --version

The output should contain “BugBuster Code 1.3.0”.

First thing to try

rm -f "$HOME"/work/bugbuster.yaml "$HOME"/.bugbuster/config.yaml
bugbuster config init

Run bugbuster config init first to set up the tool's configuration.

What it does

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

  • Read, write, edit, search and run code
    Not tested
  • Coordinate several agents in a shared workspace
    Not tested
  • Take screenshots and use vision models
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. Main function works
  4. Works offline

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

Good for

  • Read file or list directory
  • Find and replace text in file
  • Execute shell command
  • Search by regex in files
  • Capture desktop, window, or region screenshot

An alternative to Claude Code, Aider and Continue.

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 1.3.0

Differences the test machine hit

  • README: mv bugbuster /usr/local/bin/ requires root, not available in box
    In the test: Extract and install to ~/.local/bin/bugbuster (on PATH) instead of /usr/local/bin/

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.