We build a Kubernetes dashboard, so let me argue against my own product for a minute, because if the argument holds I'd rather hear it from me than from a competitor.
It goes like this. For years the reason you opened a dashboard was that a cluster is too much state to keep in your head, and you needed something to draw it so you could look. An agent doesn't look. It reads structured data, reasons over it, and increasingly acts on it. If the agent is doing the operating, then a dashboard is a horse in 1910 - still useful, clearly on the wrong side of the trend. Every hour of operations that moves into an agent is an hour nobody spends in our UI.
I think that's half right, and the wrong half is the interesting one. This isn't the agent-vs-UI-vs-CLI question we wrote about in June, which was about which surface you reach for today. It's the harder version: if agents keep climbing the autonomy ladder, what is a dashboard even for in three years?
TL;DR. The bear case is real, and it kills one specific dashboard - the one you click through to run the cluster by hand. But as agents take over the operating, the job that grows is supervising: verifying, approving, auditing, and rebuilding your bearings at 3am when an agent hands you something strange. That job needs a purpose-built visual surface as much as flying ever did. The dashboard doesn't die. It flips from the cockpit you fly to the tower you watch from.
