Debug prod pods and docker-compose with Cursor

Reported experience

1. 1

   What they did

   With a Kubernetes MCP enabled in Cursor, Rajesh Sood asks in plain language for the logs of a named prod pod. Cursor pulls them and suggests fixes without him running kubectl. For a broken docker-compose.yml, he turned on the agent setting that runs commands automatically. He told it to keep retrying a compose dry-run until the build errors cleared.

2. 2

   How it went

   The author says the agent iterated on its own until the compose file passed. The article gives no numbers, and no example output from the prod log debugging.

3. 3

   Worth knowing

   He says Cursor once hallucinated secrets from a .env file; adding .env to .cursorignore fixed it. He also advises committing often, because agent changes can go wrong.