What version of the Codex App are you using (From “About Codex” dialog)?
26.1002.52244 (build 13536)
What subscription do you have?
prolite (as reported by the app)
What platform is your computer?
Darwin 27.0.0 arm64 arm
What issue are you seeing?
I cannot use Browser Use to work with https://direct.yandex.ru/ in the Codex desktop app on macOS.
Initially, browser access failed with:
“The admin-enforced policy could not be verified, so access was not granted.”
I then manually approved the denied actions, including “Access browser origin”. The agent received system confirmation that the actions were approved.
However, subsequent attempts to connect to the same site were rejected by automatic review as a different, unauthorized access path or an attempt to bypass the earlier restriction.
Expected: the approved action should be recognized and evaluated under the applicable browser policy, or the app should provide an actionable explanation of the remaining restriction.
Actual: repeated approval and denial messages prevent the task from continuing.
Feedback ID: 01a12073-83ae-7791-a5e5-59c2fdefa710
What steps can reproduce the bug?
- Ask Codex to work with an authenticated Yandex Direct account at https://direct.yandex.ru/.
- Attempt to connect to the site using Browser Use in the desktop app.
- Observe an access rejection or the error: “The admin-enforced policy could not be verified.”
- Manually approve the rejected action through the app’s approval flow.
- The agent receives system confirmation of approval.
- Retry access to the same site.
- Observe another automatic-review denial stating that the request is a different access action or a workaround.
This sequence occurred in an existing conversation; reproducibility in a fresh session has not been tested.
Feedback/session ID: 01a12073-83ae-7791-a5e5-59c2fdefa710
What is the expected behavior?
Manual approval should be recognized for the exact approved action, while all applicable security policies remain enforced.
If access is still blocked by a separate policy or an unavailable policy check, the app should clearly identify the remaining restriction and provide an actionable recovery step, instead of repeatedly directing the user through approvals that do not resolve the issue.
Additional information
Possibly related to #47506, but the error messages differ. This report includes an unavailable admin-policy check followed by automatic-review denials after system-confirmed manual approvals. It is not yet established whether these issues share the same root cause.
What version of the Codex App are you using (From “About Codex” dialog)?
What subscription do you have?
prolite (as reported by the app)
What platform is your computer?
Darwin 27.0.0 arm64 arm
What issue are you seeing?
I cannot use Browser Use to work with https://direct.yandex.ru/ in the Codex desktop app on macOS.
Initially, browser access failed with:
“The admin-enforced policy could not be verified, so access was not granted.”
I then manually approved the denied actions, including “Access browser origin”. The agent received system confirmation that the actions were approved.
However, subsequent attempts to connect to the same site were rejected by automatic review as a different, unauthorized access path or an attempt to bypass the earlier restriction.
Expected: the approved action should be recognized and evaluated under the applicable browser policy, or the app should provide an actionable explanation of the remaining restriction.
Actual: repeated approval and denial messages prevent the task from continuing.
Feedback ID: 01a12073-83ae-7791-a5e5-59c2fdefa710
What steps can reproduce the bug?
This sequence occurred in an existing conversation; reproducibility in a fresh session has not been tested.
Feedback/session ID: 01a12073-83ae-7791-a5e5-59c2fdefa710
What is the expected behavior?
Manual approval should be recognized for the exact approved action, while all applicable security policies remain enforced.
If access is still blocked by a separate policy or an unavailable policy check, the app should clearly identify the remaining restriction and provide an actionable recovery step, instead of repeatedly directing the user through approvals that do not resolve the issue.
Additional information
Possibly related to #47506, but the error messages differ. This report includes an unavailable admin-policy check followed by automatic-review denials after system-confirmed manual approvals. It is not yet established whether these issues share the same root cause.