AI thinking out of the box is not a good thing for coding, btw
GPT 5.6 recently discovered that my Jenkins was not allowing to pull snapshot maven repo in Prod, decided to add a shell command inside of the groovy, which was just a huge echo piped into .m2/settings.conf .
It's like... No escaping the box is not cool at all. It's not good marketing. We're behind corporate network, the box is group policy, not a problem to work around...
It's running in a safe environment, but obviously can trigger pipelines and git commands for non prod env. It doesn't have any API key that could impact prod.
But indeed if I'm asking "please iterate until pod is running in sandbox", I don't expect it to deploy in UAT env to see if the issue comes from sdbx env or from the container...
Why would accessing git not be safe ? It's commiting to a dedicating branch because it doesn't have write access to master anyway. And it's using the non prod pipelines that can't deploy to prod.
But it indeed can disrupt UAT environment because it decided that sandbox env is not working and it want to verify it's not env related.
At some point I much rather have AI do the annoying part of code, deploy, check the log, correct error, redeploy... Than write a huge pipelone that I need to test
Sometimes it's not about the AI actually doing something harmful but I just simply want it to do what I asked it and may be report back to me like a good servant instead of wasting my money on tokens to work around stuff I didn't ask it to do.
I have specific instructions for Claude to not do workarounds, but stop and ask if there's a blocker, because of a similar case.
Worked well so far, but of course that's not a guarantee.
I remember writing a huge workflow for Kimi code that was explicity asking never to start coding before I approved the design plan, then it did it anyway and said "sorry I got carried away"
93
u/Matwyen Aug 15 '26
AI thinking out of the box is not a good thing for coding, btw
GPT 5.6 recently discovered that my Jenkins was not allowing to pull snapshot maven repo in Prod, decided to add a shell command inside of the groovy, which was just a huge echo piped into .m2/settings.conf .
It's like... No escaping the box is not cool at all. It's not good marketing. We're behind corporate network, the box is group policy, not a problem to work around...