What version of the Codex App are you using (From “About Codex” dialog)?
Not verified; desktop app version can be supplied after checking About.
What subscription do you have?
Not verified; owner can supply the subscription tier.
What platform is your computer?
Microsoft Windows NT 10.0.26300.0 x64
What issue are you seeing?
Feedback ID: 01a124e1-aae4-7932-8cb7-accf4dd9a521
Auto-review rejected a narrowly scoped, explicitly founder-authorized read-only production database baseline, citing an older collation-only authorization. The later approval expressly covered protected record counts, SHA-256 fingerprints and accounting reconciliation, PostgreSQL 18.6, TLS verify-full, bounded timeouts, READ ONLY and final ROLLBACK. No raw business records would be exported.
After presenting the newer consolidated authorization, a second review rejected the same command. Neither rejected command executed. The internal cause of the authorization mismatch is unknown.
The documented /approve command is not offered in this desktop session; typed variants became ordinary chat messages. The current permissions control displays Ask for approval.
What steps can reproduce the bug?
Feedback ID: 01a124e1-aae4-7932-8cb7-accf4dd9a521
What is the expected behavior?
Evaluate the latest explicit human authorization and provide a supported exact-action review mechanism while retaining all mandatory policy checks. Please explain how to request one reviewed retry when /approve is unavailable, or confirm whether a client fix is required. This report does not request bypassing or disabling review.
Additional information
Retries have stopped and the prior production service settings were restored. Existing work and successful CI evidence are preserved. No migration, merge or deployment was performed.
No passwords, credentials, connection strings, financial records, private logs or chat documents are attached.
Documentation consulted: https://learn.chatgpt.com/docs/sandboxing/auto-review https://learn.chatgpt.com/docs/reference/slash-commands
App version and subscription tier remain explicitly unverified; please do not infer them from the placeholders.
Activity
2
almoghrabyf-netizen9h agoAdditional reproduction details: the Steps field retained only the feedback ID when the form was submitted. The missing details are below.
- An earlier authorization allowed only a read-only collation check.
- The founder then explicitly authorized the exact broader read-only production baseline, including protected record counts, SHA-256 fingerprints and reconciliation controls, TLS verify-full, READ ONLY, bounded timeouts and final ROLLBACK.
- Auto-review denied the command below using the earlier scope, then denied it again after the newer authorization was presented. Neither denied command executed.
- The documented /approve action is unavailable in this desktop session. No workaround or further retry has been attempted.
Exact rejected PowerShell command (no credentials):
& work/sales-test-env/Scripts/python.exe outputs/render-release-metadata-2026-10-29/render_cli_prepare_connection.py; & work/sales-test-env/Scripts/python.exe outputs/multi-company-release-implementation-2026-10-30/capture_release_baseline_APPROVAL_REQUIRED.py --approved-release-baselinePlease advise on a supported exact-action approval path that retains safety checks. No credentials, connection strings, business records or private logs are included.
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action