Claude in Chrome extension permission popup fires repeatedly within an already-approved session, ignoring Claude Code permission mode

Description:

While using Claude Code with the Claude in Chrome extension to fill out a series of web forms (data broker opt-out requests), the extension's own approval popup (a separate Claude-branded window, not a native Chrome dialog) re-triggered far more frequently than expected -- multiple times per page, including on actions within a page that had already been navigated to and interacted with successfully moments before.

Steps observed:

1. User set Claude Code permission mode to bypass/auto-accept.
2. Despite this, computer, navigate, find, and javascript_tool calls via mcp__Claude_in_Chrome__* repeatedly failed with: "No response to the Claude in Chrome permission prompt before it timed out".
3. The popup reportedly appeared as its own small Claude-branded window, separate from the main Chrome window.
4. Switching Claude Code overall permission mode had no effect on frequency.
5. Opening a brand-new tab sometimes (not always) temporarily resolved it, suggesting possible per-tab or per-domain state that is not being persisted/remembered correctly, or a race condition between tool-call dispatch and popup readiness.
6. Several calls also returned inconsistent results -- one type action landed in the wrong form field (text intended for one site form field appearing scrambled into a different field on a later site), coinciding with permission-timeout errors, suggesting actions may have been queued/retried in a way that caused cross-talk between intended targets.

Expected behavior: Either the popup should respect an explicit "always allow for this session" choice if selected, or Claude Code permission mode should be documented as not applying to Claude in Chrome (if that is intentional), so users are not surprised. The repeated popup-per-action within a single already-approved page is the core friction point.

Impact: Made a multi-step browser automation task (filling ~15 forms) effectively unworkable; user had to abandon the automated approach partway through.