Windows: site-safety block has no supported recovery signal; request Baidu native-app upload scope ruling #53241

Please provide a supported remediation path or an explicit scope decision for the workflow below. The account owner has already authorized the upload. Repeating user permission has not established a supported recovery path.

Requested workflow

A Codex agent uses the already logged-in Baidu Netdisk Windows application to upload two newly created local review deliverables, an MP4 and a ZIP, to the owner's existing private delivery folder. The agent then verifies the completed transfer, cloud filenames, file sizes, and video playback. No public sharing or social-media publication is requested.

Verified facts

• On 2026-10-05, Browser Use refused navigation to https://pan.baidu.com before file selection or upload. This was a browser-navigation refusal, not a failed native-app transfer.
• The refusal identified site-safety policy and explicitly said that no user permission prompt or Auto-review was attempted. It also prohibited achieving the same outcome through a workaround, indirect execution, alternate browser surfaces, or policy circumvention.
• Subsequent native-app read-only observations/navigation worked. Native-app upload after this refusal has not been attempted. Read-only success is not being claimed as upload clearance.
• On 2026-10-12, the owner explicitly authorized the agent to use the Baidu Netdisk Windows application for the upload. This is user authorization, not a claimed override of platform policy.
• The configured updater reports Codex Desktop 26.1007.21434, build 13901, release channel prod, as up to date. The runtime/build of the original refusal was not established, and the blocked action has not been retested on the current build.
• An earlier in-app feedback submission has a local routed-response record. No official feedback/session receipt, engineering assignment, trackable case, or policy correction is established by that record.
• Official AI support could not supply a case-specific scope ruling, a human handoff, or a trackable case identifier. Generic Browser Use/Computer Use separation did not resolve this case.

Please answer these questions explicitly

1. Is the original denial intended to prohibit only Browser Use on this origin, or does its same-outcome restriction also prohibit the explicitly authorized upload through the official Computer Use interface to the native Baidu Netdisk Windows application?
2. If the native workflow is permitted, please provide the applicable official scope statement and the supported action by which the agent can resume without circumventing the earlier refusal.
3. If the workflow is prohibited or the classification is incorrect, please provide the supported appeal/correction route, a trackable reference, and an observable completion signal. Do not require the owner to produce clearance evidence without an available way to obtain or observe it.
4. Is there a supported policy-only status check or narrowly defined reevaluation step that does not operate the blocked website? If yes, please document its interface and limits. If no, please state what external change the agent can observe before resuming.

Expected resolution

An official, verifiable correction or scope ruling with an actionable recovery step; otherwise an explicit statement that the workflow remains prohibited, with a trackable review path. A generic statement about user permission, full access, reinstalling, or restarting would not establish a supported remedy for this denial.

Related issue: #43068 (recovery deadlock). Similar site-safety reports: #35549 and #47800. These reports are references, not proof of clearance for this case.

This report includes no account email, credentials, cookies, tokens, private session identifiers, full conversation, raw logs, local filesystem paths, or video content. Detailed original-event identifiers can be supplied through an authorized private support channel if requested.