Monthly Archive

Fixing a production error with the Flare CLI and AI, from discovery to deploy

Feb 25, 2026 By Freek Van der Herten In Oh Dear

Using the Flare CLI and its agent skill to find, fix, and resolve a production error without leaving the terminal. The AI agent looks up the latest error on freek.dev via the Flare CLI, analyzes the stack trace against the local source code, generates a fix, deploys it using bash mode, and marks the error as resolved in Flare. Learn more.

View Video

Oh Dear

Read more about Fixing a production error with the Flare CLI and AI, from discovery to deploy

AI performance reviews for your app with the Flare CLI

Feb 25, 2026 By Freek Van der Herten In Oh Dear

The Flare CLI connects to your Flare performance monitoring data and uses AI to turn it into actionable insights, right from your terminal. In this video, you'll see how a single command pulls your real performance data from Flare, then generates a full review: identifying slow endpoints, spotting error trends, and suggesting concrete fixes. Links.

View Video

Oh Dear

Read more about AI performance reviews for your app with the Flare CLI

DNS blocklist monitoring now available to all Oh Dear users

Feb 23, 2026 By Mattias Geniar In Oh Dear

Your domain is on a spam blocklist. Password reset emails aren't arriving, order confirmations land in spam, and customers are complaining that "your site doesn't work." By the time you hear about it, the damage has been building for days. We've shipped DNS blocklist monitoring to catch this early. Oh Dear now checks your domain against 11 major blocklists and notifies you the moment you're listed, with direct links to get removed.

Read Post

Oh Dear

Read more about DNS blocklist monitoring now available to all Oh Dear users

Making our docs AI-friendly: a tale of two caches

Feb 15, 2026 By Mattias Geniar In Oh Dear

Our documentation, FAQ, and blog posts can now be served as clean markdown to AI agents. Send Accept: text/markdown or append.md to the URL, and you get structured content instead of a full HTML page. It worked great in development. Then we deployed, and two separate caching layers broke everything.