I am using claude code and I try to use it with chrome extension. It is not reliable. usally I prompt something like use /chrome to check design. Sometime it does work and times he tells me that he is unable to connect to the extension. I open and close chrome sometimes it help sometimes it does not. Usally restarting claude code helps but it really interrupts the workflow. The extension is installed and I can see the chat panel for quering during the browsing but still claude code say it is disconnected. I wonder if anyone else has this issue and if someone was able to solve itt Here are some technical details (I asked claude code to provide): Environment: - OS: Ubuntu 25.10 (Questing Quokka), kernel 6.17.0-14-generic - Desktop: GNOME Shell 49.0 on Wayland - CPU/RAM: AMD Ryzen AI 9 HX 370, 29 GB RAM - Chrome: 145.0.7632.159 - Claude Chrome Extension: v1.0.57 (Manifest V3) - Claude Code CLI: 2.1.69 (native ELF x86-64 binary, not Node.js) - Claude Model: claude-opus-4-6 - Node.js: v20.19.4 Extension details: - Extension ID: fcoeoabgfenejglbffodgkkbkcdhcgfn - Permissions: sidePanel, storage, activeTab, scripting, debugger, tabGroups, tabs, alarms, notifications, system.display, webNavigation, declarativeNetRequestWithHostAccess, offscreen, nativeMessaging, unlimitedStorage, downloads - Host permissions: <all_urls> - MCP servers config: none (empty {}) Symptom: The extension connects initially but disconnects mid-session after prolonged use. Reconnecting requires refreshing/restarting Chrome. Happens during long Claude Code sessions using browser automation (MCP) tools. Note: Wayland could be a factor — Chrome on Wayland sometimes has different IPC behavior than X11. submitted by /u/Right_Network_8833
Originally posted by u/Right_Network_8833 on r/ClaudeCode
You must log in or # to comment.