GPT 5.2's security mechanisms are excessive and hinder normal development.
Recently, I've found the security aspects increasingly frustrating. When configuring an environment, it no automatically writes configurations for me whenever key-related settings are involved.
Even test keys during development require manual configuration.
Remote SSH connections to the server via an interactive terminal occasionally fail.
Even for test keys or usernames, manual login attempts to simulate human testing are almost always rejected in version 5.2.
Furthermore, what's even more annoying is that it deletes test keys saved in my docs section. This is truly frustrating; during development, I didn't care about exposing these keys for convenience. It's very inconvenient to discover my keys are missing during testing.
Could we give users the option to choose their own security level, allowing them to take responsibility and make their own decisions?
I don't know if this excessively high security is good or bad. The advantage might be preventing negative development scenarios, but the downside... personally, I feel my normal development experience is sometimes affected because while GPT is high-quality, it's inherently slow. One feature took me 12 hours, and although it was due to a problem with my use of GPT 5.2xh, I can accept it and hope to maintain this high quality, even if it takes a long time. After all, if you clearly describe the requirements, Codex's output is truly of the highest quality, but if it doesn't meet the requirements, the time cost is also quite significant.
<img width="798" height="159" alt="Image" src="https://github.com/user-attachments/assets/45fe5755-4e12-4b58-84c1-64ca72df4b51" />
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗