One morning I asked Cowork to read the ad dashboard for one of the wallpaper apps I maintain as an indie developer. The reply was a single line: "Browser extension is not connected." The Claude icon was sitting right there in my toolbar. The side panel opened and chatted normally. And yet, from the Desktop app's point of view, nothing was connected.
My first instinct was the heavy one. I removed and reinstalled the extension, restarted Chrome, then restarted Desktop. About thirty minutes later I found the real cause, and it had nothing to do with the extension. I had closed every window of the separate Chrome profile where the extension lived the night before.
So that you don't have to start with the heaviest fix the way I did, here's the order I now check things in, split into four layers.
First, where this message actually comes from
"Browser extension is not connected" isn't an error the extension raises about itself. It's what Cowork or Claude Code says when they try to reach the extension and can't find it.
That's why a working side panel doesn't rule anything out. The side panel is self-contained inside the extension. Driving Chrome from Desktop or Claude Code needs a separate path between the two. The official help page says as much: tasks where Claude drives Chrome from another surface still need the Claude Desktop app open and connected.
Telling the cases apart is quick:
| What to check | Result | Layer to suspect |
|---|---|---|
| Can you chat in Chrome's side panel? | No | The extension itself (sign-in, plan) |
| Same | Yes | The Chrome profile, or the Desktop / Claude Code side |
Does list_connected_browsers in Claude Code return an empty array? | Empty | The profile, or the connection path itself |
Does the debug log contain upstream_403? | Yes | A layer you can't fix locally (see below) |
If the side panel works, reinstalling the extension can wait.
Layers 1 and 2: Chrome, then the profile
The first layer is whether Chrome is running at all. It sounds almost too basic, but Cowork's browser work assumes Chrome is open. The help page also says background workflows keep going "as long as Chrome is open."
The second layer is the one that caught me. Extensions are installed per profile. I keep Claude in Chrome in a dedicated work profile so it never shares a window with sensitive tabs. Even with Chrome open on my everyday profile, if the work profile had no windows, the extension simply didn't answer in my setup.
I opened one window in the work profile, sent Cowork the same request again, and it started reading the page as if nothing had happened.
While you're here, it's worth confirming that the extension is signed in to the same Claude account as Desktop or Claude Code. If the accounts differ, both sides can be healthy and still never meet.
Layer 3: Desktop has two switches, not one
The third layer is the Desktop app, and it has two steps that are easy to half-finish.
- Click your initials in the lower left, open "Settings," then go to "Customize" and "Connectors."
- Find Claude in Chrome, click "Configure," and turn the toggle on.
- In each conversation, enable Claude in Chrome from the "Connectors" menu by the input box.
According to the help page, that per-conversation switch is off by default. Finishing the connector setup doesn't turn it on for new chats. I once looked at the settings screen, saw the toggle on, and took the long way around because of exactly this.
One more thing: Cowork also has a browser built into the Desktop app. You choose between them under "Settings," "Cowork," "Preferred browser." If you expected Chrome and the page opened somewhere else, check this first.
If the Desktop toggle won't turn on, the help page suggests restarting or updating Desktop.
Layer 4: In Claude Code, read how it stops
The fourth layer applies when you use Chrome from Claude Code. I got tired of repeating the same checks by hand, so I put them into a small macOS script that lays out the local state in one pass.
#!/usr/bin/env bash
# chrome-bridge-check.sh
# Triage for "Browser extension is not connected" (macOS)
# Usage: bash chrome-bridge-check.sh [path to Claude Code debug log]
set -u
CH="$HOME/Library/Application Support/Google/Chrome"
EXT_ID="fcoeoabgfenejglbffodgkkbkcdhcgfn" # ID of the Claude extension on the Chrome Web Store
echo "== 1. Is Chrome running?"
if pgrep -x "Google Chrome" >/dev/null; then
echo "OK: Google Chrome is running"
else
echo "NG: Chrome is not running (start here)"
fi
echo "== 2. Which profiles have the extension?"
for p in "$CH/Default" "$CH"/Profile\ *; do
[ -d "$p" ] || continue
if [ -d "$p/Extensions/$EXT_ID" ]; then
echo "present: $(basename "$p")"
else
echo "absent: $(basename "$p")"
fi
done
echo " Note: folder names differ from display names. Match them via 'Profile Path' in chrome://version"
echo "== 3. Native messaging registration"
ls "$CH/NativeMessagingHosts/" 2>/dev/null | grep -iE 'claude|anthropic' \
|| echo "Not found (Desktop / Claude Code may not have registered a host)"
echo "== 4. Local bridge socket"
ls -d "/tmp/claude-mcp-browser-bridge-$USER" 2>/dev/null || echo "Not found"
echo "== 5. Refusal reasons left in the debug log"
LOG="${1:-}"
if [ -n "$LOG" ] && [ -f "$LOG" ]; then
grep -E 'Claude in Chrome|Bridge (received|connection closed)' "$LOG" | tail -n 5
else
echo "Pass a log path to see the last five related lines"
fiThe script doesn't fix anything. It's there so you can see how far the connection gets, as a list rather than a guess. If step 2 shows the extension only in your work profile, opening that window may be all you need. If steps 3 and 4 come back empty, I'd look at reinstalling or updating Desktop or Claude Code.
Step 5 reads the log from running Claude Code with --debug. In GitHub issue #108935, people reported that the extension and the account were both fine, yet the connection still failed, with lines like these:
[Claude in Chrome] Bridge received: {"type":"error","error":"OAuth token forbidden (403) — missing scope, org access, or network not allowed by org","reason":"upstream_403",...}
[Claude in Chrome] Bridge connection closed (code: 1008, duration: 0ms)
upstream_403 means your side of the path is reaching the bridge and being refused further along. The same issue reports that logging out and back in, or flipping settings, didn't change it. If you see this line, reinstalling the extension very likely won't help.
When none of that brings it back
If all four layers check out and it's still broken, this is the order I follow:
- Restart the extension, Desktop, and Claude Code as the help page suggests, and apply any updates
- If that fails, keep the script output and the relevant log lines
- If
upstream_403is there, report it on the issue with your reproduction details, and use Cowork's built-in browser or do the step by hand in the meantime
Falling back to the built-in browser felt a little like losing at first. But I've come to think that keeping urgent work moving and finding the root cause can happen on different days. How much I let run automatically hasn't changed since I wrote "I Run Claude in Chrome on Automatic Approval and Reserve "Always Allow" for Read-Only Sites," and I didn't loosen it after the connection came back.
Reinstall only after you've looked at the fourth layer. If the heaviest fix goes first, you wake up the next morning without knowing what actually worked.
If you do one thing today, open chrome://version and note which profile has the extension. I explained why I split profiles in "Before I Open the Claude in Chrome Side Panel, I Sort My Tabs," and how I divide work between Claude Code and Chrome in "Claude Code vs. Claude in Chrome: Where I Draw the Line." Once you're connected again and want Claude Code to read console and network data while chasing a bug, "Calling Chrome DevTools for agents 1.0 from Claude Code" is a natural next step.