[BUG] Claude in Chrome v1.0.75: 'Always allow' for browser actions not honored — re-prompts on every action (~300/session)

Status Open

Reported on v2.1.158

Maintainer reply None cached

Activity 5 comments · opened Jun 10, 2026

Preflight Checklist

[x] I have searched existing issues and this hasn't been reported yet
[x] This is a single bug report
[x] I am using the latest version of Claude Code

What's Wrong?

Since the Claude in Chrome extension updated to v1.0.75 (activated on this machine ~Jun 8 2026), every browser action (browser:click, browser:type, ...) triggers the "Allow Claude to use browser:click?" dialog in the Claude Code desktop app:

~300 prompts per session, ~500/day under normal browser-automation workloads (Meta Business Suite / Ads Manager flows)
Clicking Always allow (scope chip shows "Session") does NOT suppress subsequent prompts, even within the same session — the very next action re-prompts
bypassPermissions mode has no effect (expected, as browser actions are gated by the extension layer; noted for completeness)
Before v1.0.75 the same workflows ran with almost no prompts

This is more severe than #59036 (per-domain re-prompt every session): here the in-session "Always allow" grant is not honored at all, so it re-prompts on every individual action.

What Should Happen?

Clicking "Always allow" should suppress further browser-action prompts for at least the rest of the session (ideally persisting across sessions), as it effectively did before v1.0.75.

Steps to Reproduce

macOS, Claude Code desktop app v2.1.158, Claude in Chrome extension v1.0.75 (ID fcoeoabgfenejglbffodgkkbkcdhcgfn)
Start any session that drives the browser (e.g. a Meta Business Suite flow using the computer tool)
First action shows "Allow Claude to use browser:click?" — click Always allow
The next browser action immediately shows the same dialog again
Repeats for every action (~300x per session)

Diagnostics / Ruled out on this machine

Extension LevelDB (Local Extension Settings/<id>) is healthy: compactions OK, no write errors, permissionStorage key present — not local storage corruption
Fresh sessions + global mcp__Claude_in_Chrome allow rules in ~/.claude/settings.json don't change extension-layer behavior (expected)
Reproduces across all sessions/projects

Environment

Claude Code version: 2.1.158 (Claude Code)
Claude in Chrome extension: v1.0.75 (published Jun 4 2026)
OS: macOS (Darwin 23.5)
Platform: Anthropic API
Is this a regression? Yes — worked with the extension <= v1.0.74 (early June 2026)

#56965, #53630 (earlier permission_required regressions), #59036 (per-session re-prompt), #30356 (session-scoped grants, closed not planned), #66125 (persistent-allow feature request).

View original on GitHub ↗

5 Comments

github-actions[bot] · 2 months ago

Found 3 possible duplicate issues:

This issue will be automatically closed as a duplicate in 3 days.

If your issue is a duplicate, please close it and 👍 the existing issue instead
To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

speedmaxcf · 2 months ago

same issue here

tesslf124 · 1 month ago

Same issue here. Was working fine, then I switched to using a different Google account + different Claude account, with all permission settings everywhere maximally permissive, and keep getting prompted to approve actions in Chrome. At some point it resolved itself - wish I remember which troubleshooting step worked. A week later I switched Google + Claude accounts again, and I'm back to being blocked by constant permissions requests.

speedmaxcf · 1 month ago

Same issue here. Was working fine, then I switched to using a different Google account + different Claude account, with all permission settings everywhere maximally permissive, and keep getting prompted to approve actions in Chrome. At some point it resolved itself - wish I remember which troubleshooting step worked. A week later I switched Google + Claude accounts again, and I'm back to being blocked by constant permissions requests.

I was able to fix it by downgrading to an earlier version of the Chrome Plugin (which did not have that bug) from a backup and then permanently locking that version, so that no auto update would ruin it again. Claude guided me through the whole process. Just tell your issue and it'll propably help you out.

Sirfrito · 27 days ago

Environment: Claude in Chrome extension v1.0.84 (ID fcoeoabgfenejglbffodgkkbkcdhcgfn), Chrome stable, driving sessions from the Claude side panel on claude.ai (not Claude Code / not Cowork).

Reporting that the permission regression described in this issue is still present in v1.0.84 and now affects side-panel sessions, not only bridge/Claude Code workflows. Through August 1, 2026, I ran multiple long browser sessions (30–60+ actions each: navigation, sidebar clicks, zoom, screenshots) against a single public, read-only, no-login archive site (data.matricula-online.eu) with almost no permission prompts. Beginning August 3, on the identical site and workflow, every individual browser action raises an approval prompt, and — the key observation — changing the permission mode has no effect: "Automatically approve" and "Skip all approvals" both still prompt per action, identically to Manual mode, which indicates the mode preference is not reaching the extension's permission layer at all. Clicking "Always allow actions on this site" does not suppress the next prompt. Nothing changed in my workflow or prompts between the working and broken sessions; the extension version is the only known variable. This makes multi-step browser sessions unusable (~dozens to hundreds of approvals per session). Repro: side panel on claude.ai, any multi-action task on any site (e.g., "open [URL], click through 5 images in the viewer, report what you see"), any permission mode → prompt on every action. Approved sites' shows no entries despite repeated 'Always allow' clicks.