[Windows][Browser Use] Taobao read-only product collection blocked before approval despite Always allow #53349

Please review a possible incorrect site-safety classification, or provide a supported recovery process for this authorized read-only workflow.

Requested workflow
The account owner asked Codex to search Taobao for "月子服", keep the first ten products in the current search-result order, and read their publicly displayed detail-page attributes. No purchases, messages, uploads, publishing, or account changes were requested. No product attributes have been collected.

Environment observed on 2026-10-12 (Asia/Shanghai)

• Windows 10 Pro, 10.0.19045, x64.
• Running desktop package: OpenAI.Codex 26.1007.2314.0.
• Installed diagnostic CLI: codex-cli 0.162.0-alpha.17.2.
• Browser Use connected to the user's existing Chrome through the supported extension interface. The loaded Chrome extension version was not recorded.

Observed failure
Session naming and tab inventory succeed and identify an existing https://www.taobao.com/ homepage tab. A normal read-only DOM snapshot through the same supported Chrome connection is rejected before page content is returned:

"Browser Use rejected this action due to browser security policy. Reason: The site-safety policy blocks this action; no user permission prompt or Auto-review was attempted. Browser use is not permitted on https://www.taobao.com."

The diagnostic also prohibits achieving the same result through alternate browser surfaces, indirect execution, raw CDP, or circumvention. The blocked collection workflow was stopped. No alternate collection route was attempted.

Verified permission and diagnostic evidence

• User-provided screenshots of Settings > Computer Use > Google Chrome > Manage show default Browsing = Always allow and no listed custom website exceptions.
• No browser_use section was found in the current local user config.toml.
• The documented Windows system requirements.toml and user managed_config.toml files do not exist on this machine. This does not rule out cloud or tool-side policy.
• codex doctor reports consistent installation, successful desktop app-server initialization, successful provider HTTP reachability and WebSocket handshake. It reports no locally visible recent security enforcement.
• The standalone doctor process did not inspect active-chat overrides, so its configuration summary is not being treated as proof of this chat's effective browser policy.
• Doctor has optional warnings including a node_repl environment variable absent in that standalone invocation and thread inventory discrepancies. No evidence links those warnings to the site-safety refusal; those settings were not changed.
• A bounded search of recent local desktop logs did not find a matching site-specific refusal reason. Absence of a local log entry is not clearance or proof of the root cause.

Requested resolution

1. Confirm whether the origin/workflow is intentionally restricted or needs classification review.
2. Provide a supported review or reevaluation process and an observable signal for resuming the original read-only task.
3. Clarify which policy source applies when the user-facing browsing permission already allows access and the refusal occurs before user approval or automatic review.

Related existing report: #29343
Official feedback/reporting guidance: https://learn.chatgpt.com/docs/reference/troubleshooting

Privacy and status
This report contains no account names, email addresses, credentials, cookies, tokens, private tab inventories, session identifiers, screenshots, raw logs, or local filesystem paths. No safety or permission policy was modified. The original product collection remains blocked; the report does not claim access has been restored.