Extension v1.0.69 (clean install on fresh Chrome profile). Service worker console errors

Resolved 💬 2 comments Opened Apr 29, 2026 by dmayerPLS Closed Apr 29, 2026

Same issue, macOS, Chrome (latest, auto-updated this session). Extension v1.0.69 (clean install on fresh Chrome profile).
Service worker console errors (in order):
mcpPermissions-BSnCI2j1.js:1 Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
Unchecked runtime.lastError: Cannot access a chrome:// URL
Unchecked runtime.lastError: Debugger is not attached to the tab with id: <N>
After full extension reinstall + Chrome force-quit, only Debugger is not attached remains. After full Chrome uninstall + profile reset (mv ~/Library/Application\ Support/Google/Chrome ...backup) + fresh Chrome install + fresh extension install + Claude account sign-in, same Debugger is not attached error persists.
Reproduces on every domain tested: example.com, bst.cisco.com, google.com. Not site-specific. Worked normally 2 days ago — no user-initiated changes since.
Permission state: "On all sites" granted at install time. Approved Sites list at chrome-extension://fcoeoabgfenejglbffodgkkbkcdhcgfn/options.html does not persist additions via Manage Extension, Options page, or click-to-grant. No runtime permission prompt appears anywhere in any window.
Symptom from MCP layer: every browser action (screenshot, get_page_text, navigate) returns permission_required: <domain> regardless of site or permission state.
Filing because this is the third confirmed case of this defect chain and I've fully eliminated every user-side variable.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗