Detailed Analysis
A Reddit user on r/ClaudeAI has reported an inconsistent behavior with Claude's CoWork browser automation feature, specifically involving the "Claude in Chrome" connector. The user describes a situation where CoWork functions correctly in some chat sessions but fails in newly opened chats, with Claude reporting it lacks the necessary permissions to interact with browser tabs — despite being able to open them. The user has already attempted standard remediation steps, including reinstalling both the Claude desktop application and the Chrome extension, without resolution. An accompanying screenshot suggests the error message is permission-related, pointing to an authorization or connection scoping issue rather than a straightforward installation problem.
The root cause of this class of issue, according to technical documentation and community research, is most likely tied to how the Claude Chrome extension registers as an automation endpoint. The extension maintains a persistent cloud connection to Claude's service, and when the same account has the extension active across multiple machines — such as a laptop and a desktop — Claude's backend routes automation jobs nondeterministically to whichever connected endpoint responds first. This explains the intermittent nature of the problem: some chats work because they happen to route to the correct machine, while others fail because they are directed to a secondary device that may lack the proper active session context. Critically, uninstalling the Claude Desktop application alone does not resolve this; the Chrome extension itself must be fully removed from any unintended machines to restore consistent routing.
The permission-failure behavior the user describes — where Claude can open tabs but cannot interact with them — aligns with a known failure mode where the automation endpoint receives the job but lacks the site-level permissions or active browser context required to execute actions. Claude in Chrome requires explicit per-site access grants, and these permissions are tied to the specific browser instance where they were configured. If the job is routed to a different machine or browser profile (including unintended installations like Chrome Canary), the permissions granted on the "correct" machine are simply not present, causing Claude to stall at the interaction step.
This issue reflects a broader architectural tension in cloud-connected browser automation tools: persistent background connections enable powerful cross-device functionality, but introduce ambiguity about which device should serve as the active execution environment. Anthropic's CoWork feature is relatively new, and the current implementation lacks a user-facing mechanism to designate a preferred automation device or to view which endpoints are actively registered under an account. The absence of this control surface forces users to diagnose multi-device conflicts manually, which is a non-trivial task for non-technical users.
The problem also highlights an emerging set of challenges in agentic AI deployment, where AI systems must reliably maintain state and permissions across sessions and devices. As Claude and similar models take on increasingly autonomous, multi-step tasks in live browser environments, the reliability of underlying connector infrastructure becomes critical. Anthropic's support documentation does address several Chrome-related failure modes, but the multi-machine routing conflict specifically remains a gap that the platform will likely need to address with more explicit device management tooling as CoWork adoption scales across Pro, Max, Team, and Enterprise plans.
Read original article →