Julian Neagu

Love that the agent learned to leave room for a rider after getting it wrong the first time. That’s the kind of small fix worth adding to the rules so the next run gets it right.

The part about cached UI vs actual offline functionality is important. I've seen how easy it is to assume offline support means everything still works. Being clear about what needs a connection saves users a lot of confusion.

I've seen the same thing with small tools. It's easy to focus on hiding the logic, but trusting a price from the browser is the bigger mistake. Always let the server have the final say.

The bit about asking before recommending really hits home. I’ve seen AI tools make confident guesses when one simple question would’ve saved everyone time. Getting the right context first makes all the difference.

The fallback point hits home. Most apps are built for the happy path, then one service goes down and everything starts piling up. Returning something useful beats showing a 500.

Love the focus on understanding existing apps, not just generating new ones. That’s where AI agents could save devs a ton of time, especially when the project has years of logic behind it.

The part about hashes showing changes that don't actually matter is so real. I've run into the same thing with tools that compare generated output. Getting a clean diff is harder than it looks.

The audio never leaving the phone is a big deal for apps handling private stuff. Nice to see offline speech getting fast enough to feel usable on a normal phone.

The vendor-independent part feels like the real win here. I've built enough small AI tools to know how annoying it gets when useful context is stuck in one place. Keeping it portable makes a lot of sense.

I’ve seen similar issues when building small HTML tools. The page can look totally fine while the raw output tells a different story. Checking what the agent actually reads feels like a step we’ve been missing.