[Windows][Browser Use] No supported revalidation path after setting air.1688.com to Always allow following a site-safety denial

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

Not captured for this report.

What subscription do you have?

Not provided.

What platform is your computer?

Windows desktop app, using Google Chrome.

What issue are you seeing?

I authorized Codex to read my own 1688 purchase orders and save the order print pages as local PDFs. The workflow does not involve making payments, confirming receipt, requesting refunds, contacting sellers, or changing orders.

The workflow was blocked. I used the official website permission settings to set the relevant 1688 sites to Always allow, but the task still could not proceed. The app does not clearly explain whether this setting applies to the restriction or how to request a supported review after changing it.

Affected domain: air.1688.com.

What steps can reproduce the bug?

Observed user workflow:

1. Ask Codex on Windows to read an existing 1688 purchase order in Chrome and save its print page as a local PDF.
2. Encounter an access restriction.
3. Set the relevant website to Always allow through the app's website permission settings.
4. Observe that the workflow remains blocked, without a clear supported revalidation or review path.

What is the expected behavior?

Please clarify whether this read-only workflow is supported, and explain the relationship between website permission settings and site restrictions.

If Always allow cannot enable this workflow, the permission UI should make that clear and direct the user to the appropriate review or support process. This request is for a supported resolution, not for bypassing restrictions.

Additional information

Related: #45346 reports an initial 1688 access restriction on macOS. This report concerns the Windows permission-change and revalidation experience. Please consolidate if appropriate.

The official troubleshooting page directs users to this repository:
https://learn.chatgpt.com/docs/reference/troubleshooting#feedback-and-logs

This public report contains no feedback/session identifiers, exact event timestamps, internal tool transcripts, private screenshots, order contents, credentials, or financial documents.

Start by comparing the Windows workflow described here with related issue #45346 and review the linked troubleshooting guidance. Determine whether changing the 1688 site permission should trigger revalidation, and document or implement a supported path that clearly explains the restriction and next step.