[macOS][Browser Use] www.pixiv.net blocked by site-safety policy despite explicit permission
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
ChatGPT/Codex desktop app 26.901.41123 (CFBundleVersion 7942); bundled Codex CLI 0.153.3.
What subscription do you have?
ChatGPT subscription (exact tier is not shown in the app).
What platform is your computer?
macOS 27.0 (Build 26A5425a), Apple Silicon (arm64).
What issue are you seeing?
Codex Browser Use blocks the public Pixiv home page at https://www.pixiv.net/ with the site-safety policy even after the user explicitly adds the website in Settings and allows browsing.
The failure occurs before the in-app browser loads the page and before any user permission prompt or Auto-review is attempted.
Full error:
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.pixiv.net.
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.
This appears to be a false positive or an overbroad site-status classification. The same URL is reachable normally in Safari and through an ordinary read-only HTTPS request.
What steps can reproduce the bug?
- Open the Codex desktop app on macOS.
- Open Settings > Browser.
- Add
https://www.pixiv.netas a site-specific permission and enable Browse. - Start a task and ask Codex to open
https://www.pixiv.net/in the in-app browser. - Browser Use rejects the request immediately with the site-safety policy error above.
- No permission prompt or Auto-review is offered, and the explicit site permission does not change the result.
The requested action is only to open and inspect the public home page. It does not involve login, messaging, uploads, downloads, purchases, or account changes.
What is the expected behavior?
Browser Use should honor the explicit website permission and allow read-only access to the public Pixiv home page, or present a recoverable permission/Auto-review path.
If this URL is intentionally restricted, the app should explain that the user-created site permission cannot override the site-safety policy instead of showing the site as allowed while rejecting it at runtime.
Additional information
No Pixiv-specific issue was found before filing. These existing reports appear to describe the same class of site-status false positive on other legitimate domains:
- #42246 —
seller-id.tokopedia.comblocked despite site permissions - #42019 — false-positive
site_status_blockedforwww.avito.ru - #40354 —
campus.163.comblocked while a related recruiting hostname works
No account screenshots, credentials, browsing history, or private page data are attached.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Browser Use rejection for https://www.pixiv.net/ after adding its explicit site permission, then trace the site-safety policy and permission handling. Compare this behavior with reports #42246, #42019, and #40354; done means the permission is honored or the UI clearly explains why the policy cannot be overridden.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, rust
- Domain
- desktop, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100