Operations | Monitoring | ITSM | DevOps | Cloud

You've felt it. You're deep in a flow state with Claude or Cursor, building the next great thing, and then you hit the wall. Time to leave your editor, open a browser, click through a console, copy a connection string, paste it back, and pray you didn't fumble a character. The vibe is gone. What if your AI agent could just... do it? Deploy the database. Create the Kafka topic. Ship the app. All without you ever leaving the conversation. Today, that's real.

Engineering teams are shipping more AI-generated code than ever, but at what cost? Learn how to build a telemetry pipeline to monitor Claude Code usage and costs directly in SquaredUp. It is estimated that 85-90% of engineering teams are now using AI coding assistants such as Claude, Codex and Cursor. This is not just for small-scale pilot projects— around 40% of all code now being shipped is AI-generated, and in start-ups the figure is around 95%. This can result in incredible productivity gains.

Picture this. It's the end of the financial year. Your audit team is clipboard in hand, walking floor to floor, cross-referencing serial numbers against a spreadsheet that was last updated six months ago. Three days in, two people are still checking warehouses, and someone has already found a printer that the system says was disposed of in 2022. This is how most enterprises still run their physical asset audits in 2026.

AI models can reason over language, summarize findings, and explain patterns. What they cannot do on their own is see the real-time operational state of your environment. Ask a model about a critical incident and it will answer from whatever context it is given, which means the answer is only as trustworthy as the input. In operations and compliance workflows, an answer is only useful if it is grounded in current service context and governed access to the systems that define reality.