openai / openai/codex

Chrome usage failed due to admin enforced policy

Open
#41,334 9 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

app browser bug safety-check windows-os
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What version of the Codex App are you using (From “About Codex” dialog)?

26.825.32147

What subscription do you have?

Plus

What platform is your computer?

Windows 11 64bit

What issue are you seeing?

Multiple tasks have been able to trigger Chrome debug control but codex chat reports back the following:

Chrome’s managed security gate blocked Codex from inspecting the page. The reported error was:
“The admin-enforced policy could not be verified, so access was not granted.”

This is not evidence of an extension or site code error. I could see the tab and title, but Chrome would not allow automated DOM inspection, console access, or reloads. The specific administrator policy is not exposed by the error, and I must not bypass it.

What steps can reproduce the bug?

Try to access the page I am on via a prompt, and see this issue in Codex

What is the expected behavior?

Access fine and do what you need to do

Additional information

I have used codex for several months now with no issues on the same laptop, site and setup. This is new as of a few days ago.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing Chrome debug control from the Codex App on Windows 11 64-bit using the reported prompt and check whether the admin-enforced policy error occurs. Investigate the Chrome managed security gate and verify that page inspection, console access, and reloads work when policy verification succeeds without bypassing administrator controls.

Written by the indexing model from the issue text.

Assessment

Domain
desktop, devtools, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.