I switched from my desktop to my phone mid-conversation last month, expecting to just pick up where I left off, and got a blank history list instead. Copilot chat history not syncing between devices is one of those problems that feels small until you realize you actually needed that conversation. So here’s what’s actually going on, and what fixed it for me.
Quick warning before anything else: don’t uninstall the app as your first move. Get to that later if nothing else works.
Quick Answer
- Confirm you’re signed into the exact same Microsoft account on every device — this is the single most common cause
- Check whether you’re comparing two different products: the Microsoft 365 Copilot app, Copilot in Edge, and GitHub Copilot Chat in VS Code do NOT share history with each other
- Update the app or browser — version mismatches between desktop and mobile cause real sync gaps
- Clear local cache, then sign out and back in on the affected device
- If history is missing rather than just delayed, escalate to Microsoft support with a specific date range — this can be a backend issue that only support can fix
Why It Fails
There isn’t one single cause here, and that’s part of what makes it annoying to troubleshoot. From what I’ve seen, it usually comes down to one of these.
Account mismatch is the most common one, and the easiest to miss. Copilot conversation history is stored and synced in the service backend and shared across devices only when you’re signed into the same account everywhere. If your phone is signed into a personal Microsoft account and your laptop is on a work account, or you’ve got two personal accounts because you made one years ago and forgot, the histories will look completely disconnected. They’re not broken. They’re just different accounts.
Version drift between platforms. One user found that an outdated mobile version of Edge’s Copilot was the actual reason history wasn’t appearing — not a sync failure, just a UI feature that hadn’t shipped to that version yet. This shows up a lot whenever Microsoft rolls out a new Copilot interface design and pushes it to web before mobile, or vice versa.
You might be looking at two different products that share a name but not a backend. This one trips people up constantly, including me the first time. Microsoft 365 Copilot (the work-license app, copilot.microsoft.com, and the mobile app) syncs chat history through a cloud backend. GitHub Copilot Chat inside VS Code is a completely separate product, and its chat history is stored locally on each machine with no built-in sync — there’s an open feature request for this, but as of now it doesn’t exist. If you’re hopping between “Copilot in VS Code” and “Copilot the assistant app” expecting shared history, that’s not a bug. It’s two different tools.
Backend index problems, which are rarer but real. Some users have reported chat history hard-locked at a specific timestamp across every device, with older chats loading fine and a chunk of recent days missing entirely. That’s not a local cache issue — cache clears and reinstalls don’t touch it, because the data sits in the service backend, and recovering it (if it’s recoverable at all) requires support-side remediation.
Common Scenarios Where This Shows Up
The exact symptom tends to vary depending on what you’re using.
On the Microsoft 365 Copilot mobile app, the typical complaint is desktop showing full history while mobile shows nothing, even with memory turned on and the same account signed in everywhere.
On Copilot in Edge, people report the opposite pattern after a UI update — each device shows its own independent history with no overlap, even though it worked fine before the redesign.
In Copilot Notebooks, sync between the Microsoft 365 Copilot app and mobile is a newer, deliberately built feature — chats started in a Notebook conversation now follow you to iOS and Android automatically, which is worth knowing because it means the feature genuinely doesn’t exist yet for every Copilot surface, just the ones Microsoft has specifically wired up.
And in GitHub Copilot Chat (VS Code), there’s no sync at all right now, by design, regardless of what device or account combination you try.
Step-by-Step Fixes
Step 1: Confirm the account first, before touching anything else
Check the account email shown in the app settings on every device you’re comparing. This sounds too basic to be the fix, but it’s the most common root cause by a wide margin.
Step 2: Identify which Copilot product you’re actually using
Microsoft 365 Copilot app, Copilot in Edge browser, and GitHub Copilot Chat are not interchangeable. If you’re expecting history to follow you between, say, VS Code and the mobile app, that’s not currently possible.
Step 3: Update everything
Update the app on mobile, update Edge on desktop and mobile, and update the Windows or Mac Copilot app if you’re using one. Version mismatches between platforms are a documented cause of sync gaps.
Step 4: Clear local cache and re-sign in
On the device with the problem, sign out completely, clear the app’s cache (or browser cache if you’re using web Copilot), and sign back in. This resolves a meaningful chunk of sync issues that are purely local and not backend-related.
Step 5: If cache clearing doesn’t help, reinstall as a last resort
Delete the app, reinstall it fresh, and let it re-sync from the cloud. This works because your history lives server-side, not on the device — a clean install just re-pulls it. That said, back up anything important first by exporting individual chats, since this step has occasionally gone wrong for people who lost mobile-only threads during a reinstall.
Step 6: If history is missing entirely, not just delayed, contact support directly
If recent days or weeks of history are flat-out gone across every device rather than just slow to appear, this is likely a backend index issue. Open a support request through the Microsoft 365 or Copilot support channel and reference the specific date range that’s missing. In-app escalation options are limited for this particular issue, so going through the formal support channel tends to get further.
What Actually Worked For Me
My case turned out to be the version-mismatch problem, but it took longer to figure out than it should have because I assumed it was a sign-in issue first. I checked accounts on both devices — same account, confirmed. So I figured cache was the problem, cleared it, signed out, signed back in. No change.
It wasn’t until I actually checked the Edge version on my phone against my desktop that I noticed mobile was a few versions behind, sitting on the stable channel while desktop had already picked up a newer Copilot interface. Updated the phone’s Edge app, and the history that had been missing for about a week showed back up within a few minutes. So in my case it wasn’t sync failing — it was a feature gap between versions that just looked like a sync failure from the outside.
Your mileage may vary here, since not every missing-history case is a version problem. But it’s worth checking before you go straight to reinstalling.
Advanced Fixes and Edge Cases
Check for split accounts you forgot about. If you’ve ever signed up for a personal Microsoft account separately from a work or school account, Copilot treats these as fully separate identities with separate history. Switching accounts mid-session on one device, even briefly, can make it look like history “disappeared” when it’s actually sitting under the other account.
Test the web version directly. Going to copilot.microsoft.com and signing in there isolates whether the problem is app-specific or account-wide. If history shows up fine on the web but not in the mobile app, that points to an app sync bug rather than a backend problem.
Export chats as a safety net before any reinstall. Most Copilot interfaces have an export or save option per conversation. Doing this before a reinstall costs a few minutes and protects you from the rare cases where a clean install doesn’t pull everything back cleanly.
For GitHub Copilot Chat specifically, don’t troubleshoot it like a sync bug. Since chat history in VS Code is stored locally by design with no sync mechanism, there’s no setting to fix. If you genuinely need continuity across machines, your options right now are manual export, copying the workspace, or just accepting that context resets per device until Microsoft ships something here.
Prevention Tips
Stick to one account per device and double-check it after any organization changes, like switching jobs or getting added to a new tenant. Keep auto-update turned on for whichever Copilot app or browser you’re using most, since version drift between platforms is a recurring cause of this exact problem. And if a conversation actually matters — something you’ll need again in a week — export or copy the key parts out manually rather than relying entirely on history sticking around indefinitely.
FAQ
Why does my Copilot history show on desktop but not mobile? Usually an account mismatch or an outdated mobile app/browser version. Check both before assuming it’s a backend issue.
Does GitHub Copilot Chat sync with the Microsoft 365 Copilot app? No. They’re separate products with separate backends. There is no shared history between them right now.
Will reinstalling delete my chat history permanently? It shouldn’t, since history lives in the cloud, but there have been isolated reports of mobile-only threads getting lost during a reinstall. Export first if anything matters.
How long does Copilot keep chat history? Up to 18 months of interactions, based on Microsoft’s own documentation on the conversation history feature.
Is there a way to manually force a sync? Not really a dedicated button for it. Signing out and back in, or refreshing the history pane, is about as close as it gets.
Editor’s Opinion
this one annoyed me more than it should have, mostly because i assumed it was the harder backend problem when it was actually just an outdated app. check versions before you panic and start clearing caches or reinstalling things. also — if you’re mixing up github copilot chat and the regular copilot app like i sort of did mentally at first, that’s not a bug, that’s just two different products that happen to share a name. learned that one the annoying way.
