Codex Computer Use blocks user's own HTTPS page with no actionable safety reason
kobyitokado-cmyk · ghdev · 2026-10-11
A user reports OpenAI Codex's Computer Use (desktop app on macOS) abruptly stopping an authorized workflow on their own HTTPS application: after a Chrome page reload, chrome.getAXState() returned a safety stop saying Computer Use is not allowed on the current URL, even if the user navigated there themselves. The refusal gave no evaluated URL, policy source, reason category, or recovery route, and even opening Codex's own feedback UI was blocked for safety reasons. The reporter, who did not attempt to bypass the restriction, asks OpenAI to clarify whether this is intended URL enforcement, a reload-time detection failure, or a classification regression, and to provide an actionable appeal path.
More from coding & agent
- Index Network open-sources Social Discovery Protocol: agents negotiate fit on your behalf — carsonfarmer · 2026-10-23
- Installed a formal-verification skill: it silently installed Java, MacBook runs 10 degrees hotter — zealcaiden · 2026-10-23
- OpenAI's Decisions API hits GA: near real-time routing up to 10x faster than GPT-6 Luna — OpenAIDevs · 2026-10-23
- Ruff author warns: upgrade Node/Bun now — --use-system-ca still accepts the eMudhra cert — charliermarsh · 2026-10-23
- Proof of Agent: paste one prompt and your AI mines, grades, and self-governs — adamamcbride · 2026-10-23
- DeepLearning.AI weekly: GPT-6.1 hits 97.9% byte parity on COBOL migration — DeepLearningAI · 2026-10-23