This has a lot of words with very little information. Having codex make changes to code because someone made a request to IT is insane, even if it needs approval.
Idk man, I feel like I am taking crazy pills.
I use codex everyday but I plan the work and codex performs the work bit by bit, which allows me to review every piece of code. I would not sleep well not knowing what is in production.
The problem with "someone makes a request, code changes happen automatically, and all someone else has to do for that to be committed is mash approve" doesn't strike me as a way to create a maintainable code-base.
The changes may even work, and may technically fulfill the request, but the agent cannot know the design intent or process intent. Today there may be a programmer sitting between the request and approval, but what about tomorrow? Might it be a non-technical or barely technical middle manager?