July 5, 2026
Bug saved, comments unleashed
sqlite-utils 4.0rc2, mostly written by Claude Fable (for about $149.25)
AI helped catch a nasty app bug, but the comments turned into a money fight
TLDR: An AI helper caught a serious bug before a software update went out, likely saving users from lost work. But commenters were more fired up about the price tag, whether AI invents problems, and even whether AI-made code is legally safe to use.
A software maker says an AI assistant helped save a major update to his database tool from shipping with a really ugly bug—the kind that could make people think their changes were saved when they actually vanished. He says the bot, Claude Fable, worked through dozens of prompts and commits, even while he was out watching a July 4 parade, and the whole adventure got packaged into a cheeky price tag: about $149.25. Naturally, the crowd immediately grabbed the number and ran in different directions.
One camp was quick to yell, “that’s not the real cost!” pointing out it came from a larger monthly subscription, not a one-off bill. Another camp was much less amused, saying that in many places, $149 could cover food, water, and utilities for a month—turning the post into an accidental debate about tech privilege. Then came the classic AI doom-and-eye-roll squad: one commenter complained these tools are too eager to please, saying if you keep asking for problems, they’ll keep inventing them and never tell you “all clear.” That sparked the bigger trust question: is AI a brilliant reviewer, or just an overconfident hall monitor?
And because no internet thread can stay normal, someone lobbed in a legal grenade about whether AI-written code can even be properly copyrighted in Europe. Meanwhile, the funniest vibe came from the people celebrating “dual wielding” bots—using one AI to check another like some kind of nerdy wizard battle. So yes, the software got safer, but the real spectacle was the comment section: price discourse, legal panic, trust issues, and meme-worthy bot-on-bot drama.
Key Points
- •The article reports that Claude Fable helped review sqlite-utils 4.0rc2 ahead of a planned stable 4.0 release.
- •A release-blocking bug was found in `Table.delete_where()`, where missing transaction wrapping could leave the connection in an open transaction and cause data loss.
- •The author says the review process involved 37 prompts, 34 commits, and 1,321 added lines with 190 removed across 30 files.
- •The new release candidate includes expanded documentation for sqlite-utils transaction behavior, stating that write operations commit automatically before returning.
- •The documentation explains that explicit transaction management is only needed when grouping operations with `db.atomic()` or managing a transaction manually with `db.begin()`.