Its theme's rank, 14 days: 8 on the Codex sheet
50 people reported
All time, since Sep 21, including 9 thumbs-up on GitHub.
Browser blocks allowed site
“Agent access to an existing internal-browser tab and creation of a fresh internal-browser tab both fail.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/codex/issues/9254/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Browser Use blocks site despite Always allow permission. The browser tool returns a saved-permission rejection without an approval prompt; the chat's session config retains a denied entry that restarting does not clear.
Is this your bug?
File my report- Where
- Browser Use
- Error text
A saved user permission setting blocks this action- Versions
- 0.146.0 to 26.1027.30824
- Platforms
- Linux, macOS, Windows
- How bad
- Breaks a normal workflow. Some reports say it blocks them completely.
Part of: Browser Use blocks allowed websites10 bugs
- Site-safety block ignores allow19 people
- Allowed site still denied10 people
- Browser Use denies allowed origins9 people
- Pinduoduo site blocked4 people
- Browser access denied after approval4 people
- Browser Use blocks vk.ru4 people
- Site-safety gate blocks Browser Use3 people
- Saved browser permissions unverified2 people
- Avito.ru blocked by site-safety3 people
Original reports41, newest first
- Windows Browser Use blocks ModelScope despite saved allowOn GitHub#59506
- macOS built-in browser retains localhost conversation denial after explicit global AllowOn GitHub#59248
- macOS Chrome: website access blocked in existing chat despite “Always allow”; new chat worksOn GitHub#58792
- Windows Browser Use: conversation denial survives explicit site Allow; supported recovery neededOn GitHub#58681
- Desktop browser origin remains denied for a chat after website permission is explicitly allowedOn GitHub#58439
- Browser blocks App Store Connect despite “Always allow” in settings and config.tomlOn GitHub#58438
- macOS Chrome Browser Use denies Amazon Ads FR/IT despite saved Always allowOn GitHub#57525
- Browser access remains denied on Linux after allowing local development site in Chrome/BraveOn GitHub#56734
- macOS iab: saved-permission denial persists despite allow settings and no effective managed requirementsOn GitHub#56469
- Windows Browser Use: per-session origin denial persists despite Always allow and full app restartOn GitHub#56028
Show all 41Show only the newest 10
- shell cloud google in browser permissions failureOn GitHub#55558
- Browser access is blocked in this chat without showing an approval prompt.On GitHub#55239
- Saved Browser Use denial cannot be revoked through the visible Codex desktop UIOn GitHub#54849
- Browser tool still denies access due to saved permission settings after the site is allowed in the built-in browserOn GitHub#54807
- macOS app: in-app browser origin gate still denies Always allow after restart (build 20586)On GitHub#54629
- In-app Browser Use still reports a saved domain block after permission changes and resetOn GitHub#54430
- [macOS 26.1007.71326] Browser Use saved-permission denial contradicts Always allow and explicit origin allowOn GitHub#54189
- # Browser Permission DiagnosisOn GitHub#53744
- Chrome blocks Supabase despiteOn GitHub#53493
- [macOS desktop] Saved Asana denial persists after website permission resetOn GitHub#53455
- macOS built-in Browser Use blocks data.stats.gov.cn despite persisted exact-origin allowance after restartOn GitHub#53364
- Browser access reports a saved Instagram block despite “Always allow” permissionOn GitHub#53320
- [macOS][Chrome] unified-computer-use / cua_repl reports a saved permission denial despite Browsing = Always allowOn GitHub#53311
- [Windows][Browser Use] Saved denial despite explicit origin allowance; declined-permission error without a visible promptOn GitHub#53031
- Codex desktop: site remains blocked after clearing visible browser permissionsOn GitHub#53025
- [Windows][Browser Use] Saved permission blocks Fastbet despite Always allow in BraveOn GitHub#52903
- Codex still blocks access to Make, even though the permission is shown as allowed.On GitHub#52861
- ChatGPT Work Browser Use broken on Windows 10 – persistent permission denial and IAB errorsOn GitHub#52485
- Desktop Browser Use saved-deny contradicts website permission UI; feedback eligibility check failsOn GitHub#52460
- [Browser Use] Chrome access denied despite explicit site permissionOn GitHub#52023
- macOS: Browser Use saved denial persists after Always allow, rule removal and restartOn GitHub#51942
- [Linux][In-app Browser] localhost rejected as saved permission block despite Always allow UI and TOMLOn GitHub#51815
- can not connect yahoo email account for chatgpt to view and reviewOn GitHub#51506
- In-app browser blocks an allowed website, and /feedback failsOn GitHub#51383
- Windows: site allowed globally but active conversation retains origin denial; no visible reauthorization pathOn GitHub#51179
- Access (to a Website) remains blocked in an existing chat after Settings is changed to “Always allow”On GitHub#51036
- macOS browser access remains blocked by conversation-level denied origin despite global/site Allow settingsOn GitHub#50789
- Desktop Browser Use rejects origin as saved Block despite UI and config AllowOn GitHub#50240
- Browser access remains blocked by a saved chat-level denial after explicitly allowing the siteOn GitHub#49453
- [macOS Desktop] Browser Use reports saved permission block despite site access allowOn GitHub#47506
- macOS built-in Browser blocks PropFinder despite explicit Browsing: Always allowOn GitHub#47131