The demos look super cool! An AI agent detects a failing deployment, rolls it back, opens a GitHub issue, and notifies Slack — all before the on-call engineer has finished reading the alert. If you’ve been following the DevOps tooling space over the last 18 months, you’ve probably seen some version of this pitch. But here’s the honest question: How much of this is actually running in production today, and how much is still a well-staged conference demo? This article cuts through the noise. We’ll look at what AI agents in DevOps actually are, where they’re delivering real value right now, where they’re falling flat, and what teams need to think carefully about before giving an agent the keys to their infrastructure. What We Mean by “AI Agents” in DevOps Before we can separate hype from reality, we need to agree on what an AI agent actually is in this context — because the term is used to describe everything from a glorified LLM wrapper to a sophisticated multi-step autonomous syst...
SUSE today revealed it is collaborating with multiple providers of artificial intelligence (AI) agents with the ability to manage IT infrastructure resources via integrations with the Model Context Protocol (MCP) server embedded in its platforms. Announced at the SUSECON 2026 conference, AI agents from Fsas Technologies, n8n and Revenium, Stacklock and Amazon Web Services (AWS) can invoke the MCP server that SUSE has embedded in its Rancher Prime and SUSE Multi-Linux Manager offerings. Rick Spencer, general manager, engineering at SUSE, said that capability makes it possible, for example, for the Amazon Quick AI agent that AWS developed to automate workflows for managing IT infrastructure resources such as Linux servers and Kubernetes clusters. Ultimately, any AI agent that can access the SUSE MCP server should be able to, for example, identify system faults in Kubernetes clusters or Linux servers, correlate system logs, and submit a pull request (PR) or a patch to restart a serv...