Dev Update: Fixing kinks in remote execution

Building in public means being honest about the "one step forward, two steps back" nature of development. If SQLitePilot is going to be the tool that stops you from "raw SQL gambling", it needs to be 100% predictable.

I’ve spent the last few days squashing three bugs that were getting in the way of that predictability.

The Fixes

• Connection Management: Previously, trying to delete a saved connection was hit-or-miss. The command would fire, but the UI wouldn't always commit the change. You can now clean up your dashboard without "zombie" connections sticking around.
• The "Ghost" Confirmation: There was a frustrating bug where you’d prepare DELETE or UPDATE command, click 'confirm' in the dialog box, and... nothing happened. The intent was there, but the command didn't always reach the remote database. That’s fixed. When you confirm an action now, it actually happens.
• Sequential Querying: One of the biggest friction points was the session timing out or failing after the first command. Previously, you often had to reload the connection just to send a second SQL command. I’ve stabilized the session handling so you can run multiple queries in a row without the "reload dance."

Reliability over features

SQLitePilot is about removing friction. It’s a GUI designed to let you manage remote SQLite databases visually via SSH, and that bridge needs to be rock solid.

These updates are live. If you’re using the app, you should see much smoother performance when hopping between your production environments.