openai / openai/codex

Browser Use cannot control Chrome: admin-enforced policy verification fails

Open
#44,621 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app browser bug
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)?

Version 26.903.61454

What subscription do you have?

Plus

What platform is your computer?

MacOS Mac Mini

What issue are you seeing?

Codex detects Chrome and the open Meta Ads Manager tab, but cannot read or control it.

The exact error is:
“Browser Use could not complete this action because a browser security check was unavailable. Reason: The admin-enforced policy could not be verified, so access was not granted. Browser use could not verify the admin-enforced policy before accessing https://adsmanager.facebook.com.”

The problem persists in new conversations. Please investigate why the security policy verification fails and how to restore authorized browser access.

What steps can reproduce the bug?

Feedback ID: 01a07c8a-13dd-7c32-9fb2-edd8c1237b39

What is the expected behavior?

Codex should verify the applicable security policy and read the authorized Chrome tab. If access is denied, it should explain the cause and provide actionable recovery steps.

Additional information

No response

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 with Feedback ID 01a07c8a-13dd-7c32-9fb2-edd8c1237b39 and reproduce in Codex App on the reported Mac Mini with Chrome open to Meta Ads Manager. Trace the admin-enforced policy verification failure; done means authorized browser access is restored or the denial explains its cause and provides recovery steps.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.