There are plenty of good SQL clients. I built another one. For a long time the honest answer to "why?" was just taste — I wanted something fast, keyboard-first, monospace-native, with no telemetry and no ceremony. A tool that gets out of the way. That's a fine reason to build for yourself, but it's a weak reason to expect anyone else to care.
Then AI agents showed up, and the question changed.
The new problem nobody's client was built for
More and more of my day runs through an AI agent. And increasingly that agent wants to touch the database — check a migration, count some rows, verify data before it writes code against it.
The naive way to give it that is genuinely alarming: hand the agent raw connection credentials, or wire up a "run this SQL" tool with no guardrails. Now a probabilistic system has an unmonitored write path to your data. One confidently-wrong UPDATE ... WHERE (or a missing WHERE) and you're restoring from backup.
