Building thoughtful software with AI.Notes from the systems behind the work.
A send-to-tracker button on the sale report matches every selected store to its own workflow before sending, builds one PDF per store, and counts sent, skipped and failed instead of showing one green banner. Plus the timeout bug underneath that left run records stuck as started.
Read moreThe SDK middleware turned every failed token check into a redirect to sign-in, so an outage on my side would have looked like a mass logout. I split the answer into yes, no and couldn't-check, and made the middleware answer an outage with a 503. In the same commit the browser client went the other way and now throws away good tokens when the server is unreachable.
The session summarizer found its work by looking for sessions with no record, so anything that failed came back on every run. Now a failure writes a stub record, the report skips stubs and counts them, and the promise in the warning got smaller to match what the code can actually do.
A deck-to-PDF exporter I wrote flattens every page into images by default, and on a reread I noticed its font and image waits always pass, so a fallback font would get frozen into pixels with nothing left to catch it.
Reading back a new export that pushes a planning document into an issue tracker, I found it keeps every created ticket ID in memory until the end, so one failed call leaves orphan tickets and a retry builds them all again.
A change adds coding-session data to my issue tracker's tickets. The tenant check held, but the panel showed stand-in values with nothing marking them as stand-ins, mislabeled a link time as a start time, let one unsynced ticket blank the whole panel, and showed a green success banner for a button that sends nothing.
Coding-agent runs moved into the background, with their logs streamed to object storage under a comment promising crash safety. Reading the diff back, the upload only becomes a file when my code closes it, so a killed run leaves no log and a row stuck on running.
Restoring a backup puts the old accounts back, including the one running the restore. The agent's first attempt saved only the admin's password; the second saved the whole account and its grants, and I walk through the gaps I can still see in the code, starting with the login rename and id reuse.
The first-run wizard check went from the root layout to the sign-in callback to a flag on the login profile, and only stopped misrouting people once the landing page and the wizard page asked the same rule about the same database row.