Claude for Chrome extension: add global 'always allow all actions' setting to bypass per-site permission dialogs

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

The Claude for Chrome extension shows a per-site permission approval dialog every time Claude Code tries to use a browser MCP tool on a new site. There is no way to globally pre-approve all actions.

The dialog has a timeout — if the user doesn't click in time (e.g. because they were in another window like a terminal), it disappears and the action is treated as denied. Switching focus to the browser window to click the dialog can itself cause the dialog to disappear, making approval nearly impossible in some UI scenarios.

For users running Claude Code from a terminal or IDE alongside Chrome, this dialog constantly interrupts the workflow. There is no "always allow all" option in the extension settings, no managed policy to bypass it, and no way to pre-authorize sessions globally.

Proposed Solution

Add a global toggle in the extension settings (or a managed policy / chrome.storage entry) such as "Always allow all Claude Code MCP actions" that, when enabled, bypasses the per-site approval dialog entirely for all Claude Code sessions. No dialog should appear; all MCP tool calls should be auto-approved.

Alternative Solutions

The Claude Code global settings.json has a permissions allow list (e.g. "mcp__claude-in-chrome__*") but this only bypasses Claude Code's own permission prompt — it has no effect on the extension's separate approval dialog. I verified this by reading the extension source (PermissionManager-BBDx9xIl.js) and the managed_schema.json, which only exposes blockedUrlPatterns and forceLoginOrgUUID — no skip-all-permissions policy.

The extension source does have a getSkipAllPermissions() function and a bypassLocalhostForMcp flag internally, but neither is user-configurable.

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

Extension version: 1.0.75 (ID: fcoeoabgfenejglbffodgkkbkcdhcgfn)
OS: Windows 11 Pro
Workflow: Claude Code running in a terminal/IDE (Sublime Text with Terminus), Chrome open separately.

The dialog appearing in a background window creates a race condition: the user must switch focus to Chrome to approve, but switching focus sometimes dismisses the dialog, registering as a denial. This makes the extension nearly unusable in a multi-window development setup. A simple "trust all Claude Code sessions" toggle would completely solve this.