Operations | Monitoring | ITSM | DevOps | Cloud

AI coding tools were supposed to mean developers work less. On a recent webinar recorded with LeadDev, senior engineering manager Vernon put words to something a lot of teams are quietly noticing instead: “It’s concerning because it’s the opposite of what was promised. We were supposed to be working less.”

We just added two new AI features to our app: natural-language translation for Error search and Insights queries. Honeybadger has two query languages: Error search speaks a simple token syntax in the spirit of Solr or a basic Elasticsearch query, while Insights runs on BadgerQL (BQL), our own language for digging into your event data, designed to feel familiar to CloudWatch Insights and Splunk users. Both are powerful, but sometimes you just want something that works without having to open up the docs.

AI agents are quickly becoming part of the enterprise automation conversation because, among other things, they help teams move faster. But there is a major difference between an AI agent that sounds useful in a demo and an AI agent that is ready for production. Production agents need scope. They need to know what they own, which systems they can touch, which workflows they can run, which teams they support, and where the boundaries are.

When we launched our Governance Gap series, we set out to explore how the explosion of AI-assisted engineering changes the risk profile for modern software organizations. We looked at the rise of The New Software Creator and analyzed why deployment governance is what keeps teams safe when code production accelerates. We also mapped out the realities of security at scale and defined who owns governance accountability.

When we introduced the Low Code Plugin (LCP) framework in February, the premise was simple: if a system has an API, you should be able to build a plugin for it — quickly, with minimal code, and in a way you can share with the community. The "AI-ready" part was deliberate. The framework was designed to work naturally with AI assistants, so the path from idea to working integration would be as short as possible. That design decision is now paying off.

Anthropic, the company behind Claude, ran the most honest experiment in agentic AI: they gave a version of their own model $1,000, a small fridge in the office lunchroom, and one job. Run a shop. Make a profit. They named it Claudius. Claudius did not make a profit.