The coding agent on your laptop is also your ops team

The 4 PM alert says the worker is wedged. You're deep in the other task, so you type one line to the coding agent on your laptop: check the worker on staging.

It has no ops tooling installed. It doesn't need any. It curls the daemon's status endpoint and sees the program flapping. It queries the logs endpoint with level=error and reads the last fifty entries. It snapshots the container: evidence, and an undo: fixes the bad env file, then stops and starts the program through the daemon endpoints. It hits the health URL: 200.

The agent that writes your code just did your ops, using the HTTP client it already had.

You didn't give the agent an ops tool; ops was already speaking its language.