Claude in Chrome: options.html#permissions page lacks UI to grant site permissions
Resolved 💬 3 comments Opened Jan 29, 2026 by Drew-source Closed Feb 2, 2026
Bug Description
When attempting to use Claude in Chrome with Claude Code on Windows, the extension repeatedly redirects to chrome-extension://fcoeoabgfenejglbffodgkkbkcdhcgfn/options.html#permissions but this page has no buttons or UI elements to actually grant permissions on a per-site basis.
Environment
- OS: Windows
- Claude Code version: 2.1.23
- Chrome extension: Claude in Chrome (installed, logged into same account as Claude Code)
- Chrome site access setting: Already set to "On all sites"
Steps to Reproduce
- Install Claude in Chrome extension
- Start Claude Code with
/chromeenabled - Attempt to use browser automation tools (e.g.,
tabs_context_mcp) - Extension redirects to
chrome-extension://fcoeoabgfenejglbffodgkkbkcdhcgfn/options.html#permissions - No UI exists on this page to grant permissions
Expected Behavior
Either:
- The
options.html#permissionspage should have a functional UI to manage site permissions - Or the extension should use the side panel permission flow instead of redirecting to this dead-end page
Actual Behavior
tabs_context_mcpreturns "Browser extension is not connected"- Extension keeps redirecting to the options page with no actionable UI
- Cannot establish connection between Claude Code and Chrome despite:
- Extension installed and enabled
- Logged into same account
- Site access set to "all sites"
- Chrome and terminal restarted multiple times
/chromecommand run multiple times
Attempted Workarounds (None Worked)
- Restarting Chrome completely
- Restarting Claude Code / terminal
- Running
/chromemultiple times - Setting site access to "all sites" in extension settings
- Trying to access permissions via side panel (three dots -> Settings -> Permissions)
Additional Context
The permissions guide documents a permission flow through the side panel, but the actual behavior redirects to an options page that lacks the documented UI elements.
This may be related to:
- #21300 (Windows connection issues)
- #20683 (MCP bridge conflicts)
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗