Should AI agents be able to see what the application is actually doing?

One thing I've noticed with AI coding agents is that they can be really good at working with source code, but that's only part of the problem when you're building a real application. You can have perfectly reasonable-looking code and still have a broken application because a container isn't running properly, a service is listening on the wrong port, an environment variable is missing, or two services aren't communicating correctly. That's where I think runtime awareness gets interesting. While working with IQX.DEV. I've been exploring the idea of an agent that can look beyond the codebase and inspect things like container logs, running processes, ports, endpoints and service connections. Instead of the agent simply changing code and hoping the problem is fixed, it could potentially follow something closer to: inspect → diagnose → change → run → verify For example, if an API isn't responding, the agent could first determine whether the problem is actually in the code or whether the API container isn't running, the port is wrong, or a dependency isn't reachable. But giving an agent this kind of access also raises some serious questions. How much control should an AI agent have over a running development environment? Should it be able to restart containers automatically? Change environment variables? Rebuild services? Or should potentially destructive actions always require approval? I'm curious how people building AI agents are thinking about the boundary between code generation and actual system operation.