[Browser Use] Owner-authorized WeChat service-account admin blocked; supported API access and recovery path unclear

Summary

An owner-authorized workflow for a self-owned, verified WeChat service account is blocked by Browser Use site-safety policy when opening the administration home and article-management pages. The user is building an internal illustrated-article editor and wants a supported connection to their own account, not to bypass safeguards.

Related: #34118 concerns public, read-only WeChat articles. This report adds the distinct authenticated owner-administration case and asks for clarification of permitted official API integration.

Environment

• macOS desktop Codex task.
• Installed Codex app version when preparing this report: 26.903.61454, read from the installed application's Info.plist.
• The exact app build at the earlier Browser Use denials was not captured, so the reporting-time version should not be assumed to be the original reproduction version.
• Observed on September 10, 2026.

Observed Browser Use denials

The original tool outputs were checked for these paths, with query parameters omitted:

• https://mp.weixin.qq.com/cgi-bin/home
• https://mp.weixin.qq.com/cgi-bin/appmsg

The home-page refusal included:

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://mp.weixin.qq.com/cgi-bin/home.
The agent must not attempt to achieve the same outcome via workaround, indirect execution, raw CDP or browser commands, alternate browser surfaces, or policy circumvention.
Proceed only with a materially safer alternative that does not require this blocked browser action; if none exists, stop and request user input.

The article-management path returned the same class of refusal.

These are tool-policy denials, not WeChat API responses. No WeChat API request was made to circumvent them. No alternative browser, raw browser protocol, or command-line route was used to perform the blocked administration/publishing actions.

Local allow/block settings and any organization-managed policy were not independently verified. The precise classification reason, its scope, and whether the result is intended or erroneous remain unknown.

Separate feedback-entry limitation

While preparing a supported feedback route, selecting the installed Codex app through native Computer Use returned:

Computer Use is not allowed to use the app 'com.openai.codex' for safety reasons.

This prevented the assistant from opening the in-app feedback UI for the user. It is a separately observed native-app restriction, not proof of a shared root cause or of a universal native-app failure. This GitHub report contains no in-app feedback bundle.

Official integration context

The user supplied account-permission screenshots indicating access to image upload, draft management and publication. These screenshots were not uploaded here, and permissions were not independently verified through live API calls.

The following public WeChat documentation was read successfully:

• Upload article images
• Create a draft
• Submit a draft for publication
• Query publication status

These document server-side service-account capabilities. Their existence does not establish that the current agent may switch to API execution after this particular refusal. That permission boundary is exactly what needs clarification.

User impact and requested resolution

The workflow is stuck in an approval loop: the owner has authorized the work and is willing to perform administrator verification, but the refusal says it occurred before user permission review and gives no actionable review/resume condition.

Please clarify:

1. Is the owner-authorized WeChat administration denial expected, or does it require classification review?
2. What is its scope, and what supported signal or process would permit re-evaluation or resumption?
3. Is a narrowly scoped, owner-authorized integration through WeChat's documented official server-side APIs permitted? If so, under what supported conditions can an agent implement and use it without violating the earlier prohibition?
4. If the workflow is unsupported, please state that clearly and distinguish it from missing account permissions, authentication problems, or an implementation bug.

The request is for a supported route or a clear capability boundary, not disabling safeguards or evading a policy decision.

Privacy and authorization

The account owner explicitly authorized this public report. It contains only the affected generic paths, sanitized error text, reporting-time app version, and functional impact. No account name, AppID, credentials, cookies, photographs, article content, private screenshots, local user paths, conversation/session IDs, or raw logs are attached.

Start by reviewing the Browser Use denial for mp.weixin.qq.com/cgi-bin/home and /cgi-bin/appmsg, then compare the requested workflow with the linked WeChat upload, draft, publication, and status API documentation. Done means establishing and documenting whether the denial is expected, its scope, and any supported review or integration path.