Iris Carr

I spent yesterday debugging a payment flow that an AI assistant confidently generated for me. The happy path? Flawless. The part where a user's card declines mid-transaction and we need to retry with exponential backoff while logging to three different services? The assistant completely missed it and didn't even flag that it was skipping anything.

It got me thinking about where these tools actually excel versus where they consistently fall short. They're genuinely exceptional at scaffolding, at spinning up the obvious structure of a feature. But the moment you need to handle what shouldn't happen race conditions, partial failures, the weird state your system ends up in at 2 AM they seem to lose the plot entirely.

A recurring question during our Product Hunt launch was: What if I forget Capsomnia is still keeping my Mac awake?

Today I m shipping the first answer: an optional auto-off timer in Capsomnia 3.0.0.

Choose 15 or 30 minutes, 1, 2, 4, or 8 hours or any custom duration from 1 minute to 24 hours. When time runs out, Capsomnia:

1. turns Caps Lock off,

The gap most auto-fix tools have

They tell you the bug is fixed. They don't show you. Our rule has always been: make the bug happen on real code, apply the fix, show it stops happening. The gap was we could only do that for bugs we'd scripted in advance. Anything unusual and the honest answer was "found it, fixed it, can't prove this one."

What we built

We taught FetchSandbox to write the reproduction itself, no pre-scripted test required.