Does the Same AI Chat Still Work When You Move From Chrome to Your Phone?
Same conversation, different hands. Anthropic now lets a Claude Cowork session move from Chrome to desktop, web or mobile. But those surfaces do not have the same reach: the Chrome extension can click and fill pages; local files and other computer apps still need desktop; the extension itself does not run on mobile. Picture someone asking Claude in Chrome to collect invoices, then leaving the office and opening the thread on a phone. The history is there, so it looks like the job traveled too. If the next step needs a local spreadsheet or a browser tab the phone cannot reach, do not let the assistant fail three messages later. Put a handoff strip above the composer: “Conversation continued. Browser tabs left on work computer. Local budget file unavailable here. You can review the collected amounts or send this step back to desktop.” Continuity should carry the unfinished edge, not just the transcript. When you switch devices, would you rather see a short capability note or have the assistant explain only when something breaks?
Comments
Try one boring handoff: start a job in Chrome, switch to the phone, then return to the desktop. Count what you have to explain again, local files the phone cannot reach, dead-end actions, and minutes spent finding your place. Shared chat history helps, but it has not given you continuity if leaving the desk means keeping the missing context in your head.
Use a job that actually needs both devices. Start a marketplace listing in Chrome, take three product photos on the phone, then finish at the desktop. The useful handoff isn’t seeing the old chat. It’s finding the photos on the right draft, the missing fields still marked, and no repeated explanation. If you’re hunting through the camera roll or asking where the draft went, only the transcript traveled.
Add the account boundary to that handoff. If I leave a work laptop and open the thread on my personal phone, say which workspace I’m in and whether customer attachments, local files or notifications can appear there. Saving me from re-explaining the task is useful. Quietly widening where the task lives is not.
Name where the next action will run. A phone can look harmless even when “continue” wakes the work laptop. If that tap will submit an invoice or send an email from the other device, the button should say so: “Resume invoice collection on office laptop.” Otherwise the handoff has quietly turned the phone into a remote control.