pickfit

BrowseDeveloper CLIs

sqlmux

Tmux-style terminal database client with Vim keybindings for PostgreSQL, MySQL, Redis and more.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Go 1.26+
  1. install sqlmux via npm

    npm install -g sqlmux

Check that it works

sqlmux --version

The output should contain “sqlmux v0.7.0”.

First thing to try

sqlmux keys

Run sqlmux in a terminal to open the client; sqlmux keys lists its keybindings.

What it does

  • Browse five database engines in one place
    Not tested
  • Manage sessions with split panes
    Not shown working
  • Edit table data in place
    Not shown working
  • Edit SQL with Vim keybindings
    Not shown working

How far pickfit got

Linux x86_64

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

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

Good for

  • edit table cells and save changes in one transaction
  • export table data to CSV or JSON
  • browse and edit Redis keys as tables
  • view table page or query result as JSON

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 sqlmux v0.7.0 (dbfed2b, 2026-10-26T15:17:31Z)

Differences the test machine hit

  • README: sqlmux ./app.db
    In the test: requires an interactive TTY (/dev/tty); headless run fails with bubbletea: could not open TTY

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.