### Preflight Checklist - [x] I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) and this hasn't been reported yet - [x] This is a single bug report (please file separate reports for different bugs) - [x] I am using the latest version of Claude Code ### What's Wrong? Reproducible on/off test, 10/7/26 ~10:10–10:14 PM ET, Windows: - Claude desktop running + Claude in Chrome enabled: Google Voice web shows "Can't connec

[BUG] Claude desktop + Claude in Chrome breaks Google Voice calling (desktop AND Android)

Status Open

Maintainer reply None cached

Activity 2 comments · opened Oct 8, 2026

Preflight Checklist

[x] I have searched existing issues and this hasn't been reported yet
[x] This is a single bug report (please file separate reports for different bugs)
[x] I am using the latest version of Claude Code

What's Wrong?

Reproducible on/off test, 10/7/26 ~10:10–10:14 PM ET, Windows:

Claude desktop running + Claude in Chrome enabled: Google Voice web shows

"Can't connect your call – Google Voice couldn't place your call" for many numbers.
Voice Android app (T-Mobile) also fails to place calls.

Quit Claude desktop + remove extension, no other change (same Voice tab, no reload):

calls work immediately on web and Android.

Re-launch Claude desktop + re-enable extension, same tab: calls fail again.

Notes: failure is intermittent while Claude runs (one call succeeded at 9:46 PM).
Voice page also logs repeated extension messaging errors:
"A listener indicated an asynchronous response by returning true, but the
message channel closed before a response was received."
Account: Google Workspace with a Google Voice number.

Platform: Anthropic (claude.ai, Claude desktop app plus the Claude in Chrome extension)

Operating System: Windows [10 or 11, from Settings → System → About]

Terminal/Shell: N/A. No terminal involved.

Additional Information:

Not a coding issue. Running the Claude desktop app and the Claude in Chrome extension together causes Google Voice outbound calls to fail on the web client and on the Google Voice Android app on the same account, even though the phone is on cellular and nothing Claude-related runs on it. That suggests whatever Claude does in Chrome or on the desktop affects the Google account or session server-side. Reproduced with a strict on/off test (Steps to Reproduce above). Error: "Can't connect your call – Google Voice couldn't place your call." The Voice tab logs repeated extension messaging exceptions ("message channel closed before a response was received"). Google Workspace account; Google Voice number. Happy to provide extension service-worker logs and desktop app logs.

Screenshots: Attach a screenshot of the "Can't connect your call" popup. Add the extension's Errors page from chrome://extensions if it shows any.

What Should Happen?

claude desktop with extension should not cause google voice to fail nor cause any strange computer behavior (i.e. I have noticed hands or time clock hanging etc but google voice is most important now).

Error Messages/Logs

when claude desktop and clause chrome extension connected ... google voice calls mostly do not work. After closing both voice call always work fine ... when it does not get "Can't connect your call
Google Voice couldn't place your call to ‪(336) ...." also extends to android devices too and cause calls to fail on phones too until disconnecting both claude desktop and chrome extension...use to not to this and just started within a week ago or so...

Steps to Reproduce

On Windows, install the Claude desktop app and sign in.
Install the Claude in Chrome extension, connect it to the desktop app, and leave both running.
In Chrome, open voice.google.com, signed in to a Google Workspace account that has a Google Voice number.
Place an outbound call from the Voice web dialer to any US number.
Result: most attempts fail with "Can't connect your call – Google Voice couldn't place your call to (number)". The Android Google Voice app on the same account (T-Mobile, cellular) also fails to place calls. The failure is intermittent: one call succeeded at 9:46 PM ET while both were running.
Without reloading or closing the Voice tab and without changing anything else, quit Claude desktop completely (confirm in Task Manager) and remove or disable the Claude in Chrome extension.
Place a call to the same number from the same Voice tab, then one from the Android Voice app.
Result: both calls connect immediately.
Relaunch Claude desktop and re-enable the extension. Don't reload the Voice tab.
Call the same number again from the same tab and from the Android app.
Result: both fail again with the same error.

Additional context:

Reproduced 10/7/2026, about 10:10–10:14 PM ET, and on multiple earlier occasions.
With either component running alone, calls still fail. Only removing both restores calling.
The Voice tab console repeatedly logs the exception "A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received" (9:48, 10:07, 10:09 PM ET).
No Voice-specific error appears in the console when a call fails. The rejection comes from Google's servers.
Whether the extension's debugger is attached to the Voice tab makes no difference: calls failed both with and without it.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

Claude Code Version: N/A. I'm not using the Claude Code CLI. Affected components: Claude desktop app: [version from the Claude app's Help → About menu] Claude in Chrome extension: [version from chrome://extensions] Chrome: [version from chrome://settings/help]

Claude Code Version

Desktop app version 2.26454.2

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information