Claude in Chrome Sessions Now Sync Across Desktop, Web, and Mobile

Claude in Chrome has spent its first weeks in beta as a single-tab tool: open the side panel, work a browser session, and that session stayed exactly where it started. On August 13, 2026, @claudeai announced on X that this is no longer true. Claude in Chrome sessions now carry over to desktop, web, and mobile — conversations are saved, and skills and connectors configured for the browser work the same way wherever you pick the session back up.

It's a small-sounding change with a real practical consequence for anyone using the Claude in Chrome extension for actual work: start a research task, form-fill, or CRM cleanup in a browser tab at your desk, then check on or continue it from the Claude mobile app later, without re-explaining context from scratch.

TL;DR

What actually moved: from tab-scoped to account-scoped

Before this update, a Claude in Chrome session was effectively bound to the browser instance that opened it. Close the tab, switch machines, or open Claude on your phone, and you started fresh — no memory of what the browser session had already done or found.

The account-level shift Anthropic shipped now applies to Claude in Chrome specifically: sessions are saved with your account rather than with any single device. Anthropic frames it around a simple use case — "you can start in a tab and pick it up later somewhere else" — but the mechanism behind it is the same one already running Claude Cowork: the side panel now runs the same underlying Cowork session as the desktop, web, and mobile apps, rather than a separate browser-only session object.

Two things travel with the session, per Anthropic's announcement:

• Conversations — the actual chat history and task state from a browser session
• Skills and connectors — anything you've configured for Claude to use inside the browser now behaves consistently when the session continues elsewhere

Who has it, and when Pro gets it

This follows the same tiering pattern as the extension's model access: Claude in Chrome already gates model choice by plan — Pro gets Haiku 4.5 only, while Max, Team, and Enterprise can select Sonnet 4.5 or Opus 4.6. Max and Team getting the feature-complete rollout first, with Pro trailing by weeks, is consistent with how Anthropic has staged other Claude in Chrome capabilities since the beta opened.

Why this matters more than a convenience feature

A browser agent that only remembers what happened in one tab is a tool you have to babysit start-to-finish, in one sitting. That's a real limitation for the kind of work Anthropic pitches Claude in Chrome for — pulling numbers out of analytics dashboards, organizing Drive folders, researching meeting attendees, running competitor research, clearing an inbox. Those tasks rarely fit into a single uninterrupted session, and until now, stepping away meant losing continuity.

Session portability also changes how Claude in Chrome fits into a multi-device workday. The same pattern already shows up in Claude Code's mobile remote control, where a coding session started on a desktop can be checked on or steered from a phone. Claude in Chrome catching up to that model means browser-based agent work stops being desk-bound in the same way coding-agent work already isn't.

What doesn't change

Cross-device sync is about where session state lives, not what Claude is allowed to do inside a browser tab. Anthropic's existing safety posture for Claude in Chrome is untouched by this update:

• The same site blocklists (piracy, adult content, no HIPAA-covered orgs) still apply
• The same hard-coded action bans — no stock trades, no CAPTCHA bypass, no typing sensitive data into card or SSN fields — still apply
• The same screenshot pipeline — whatever's visible in the active tab becomes part of the conversation — still applies, on whichever device continues the session
• Anthropic's own guidance that prompt injection is "the biggest risk facing browser-using AI tools" and "the risk is not zero" still stands; see the ShadowPrompt vulnerability for what that risk has looked like in practice

Anthropic separately published guidance on defending against prompt injection in browser agents — hidden instructions embedded in page content that try to redirect what the agent does — alongside recommended user habits, linked from support.claude.com. Session portability doesn't reduce that risk on its own; if anything, a session that now follows you across devices is one more reason to keep reviewing what a browser agent does on unfamiliar sites, rather than assuming a synced session is a vetted one.

How this fits the rest of Anthropic's browsing stack

Summary

As of August 13, 2026, Claude in Chrome sessions carry over across desktop, web, and mobile instead of staying locked to the tab that started them — conversations, skills, and connectors now travel with your account. Max and Team plans have it today; Pro is rolling out in the coming weeks. The change rides on the same underlying session layer that already powers Claude Cowork across devices, and it doesn't alter the extension's permission model, blocklists, or prompt-injection risk profile — those stay exactly as documented in Anthropic's existing safety guidance.

Related reading

• Claude in Chrome: What the Browser Extension Does (and Its Real Risks)
• How to Use Claude Cowork Safely: Official Security Guide
• Top 10 Claude Cowork Use Cases
• Claude Code Mobile: Remote Control From Your Phone
• Claude Code Desktop Browser: Built-In Web Browsing
• Browserbase Skills: Claude Code Browser Automation
• Claude vs ChatGPT for Work

Official sources: @claudeai on X — cross-device Claude in Chrome sessions (Aug 13, 2026) · Claude for Chrome product page · Use Claude in Chrome safely — Claude Help Center

Availability, plan tiers, and rollout timing reflect Anthropic's August 13, 2026 announcement and may change — check your account's Claude in Chrome settings for current access.