You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] Claude Code Mobile: Chats are not syncing with cloud web version, sometimes empty chats #10390
I have searched existing issues and this hasn't been reported yet
This is a single bug report (please file separate reports for different bugs)
I am using the latest version of Claude Code
What's Wrong?
I am using claude code on web and going back and forth between the cloud instances on both web and the mobile app. For some reason in the Claude mobile app, the cloud conversations are not syncing with the web version many times. I'll see previous parts of the conversation with nothing updating. Other times a conversation will be completely blank where I can continue the conversation on the web with no problem
What Should Happen?
Bidirecectional sync with web should be instant and always up to date. Statuses of whether claude code is active should also sync properly.
Error Messages/Logs
None
Steps to Reproduce
Make several long conversations in Claude Code Web
Open the mobile app and check to see if all chats are up to date
Claude Model
Not sure / Multiple models
Is this a regression?
No, this never worked
Last Working Version
No response
Claude Code Version
2.0.25
Platform
Other
Operating System
Other
Terminal/Shell
Other
Additional Information
Claude code on mobile should always autosync as soon as a conversation is loaded
Reacted by Krzemo, Robby Dhillon, Ernesto Gonzalez, Pär Boman and Rahal Aboulfeth
Noticed this bug months ago when I lost a bunch of data because of it back on Claude 4. Basically from what I've gathered the desktop will not update from mobile unless you refresh the page. If you have the same chat open in app and in browser on mobile they will sync every prompt, but if you prompt on desktop then it will overwrite the conversation branch you've created on the mobile app, but not the mobile browser. In the end it seems that the desktop branch (if created) will always overwrite any others. Fix, just always make sure to refresh your desktop before sending a prompt if you've used the app recently.
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.
Activity
n3t0cfg commentedon Nov 16, 2025
This is still happening. Mobile Version 1.251110.1
How to reproduce:
The following sessions from web won't appear in the mobile app.
treeHzme commentedon Nov 20, 2025
Noticed this bug months ago when I lost a bunch of data because of it back on Claude 4. Basically from what I've gathered the desktop will not update from mobile unless you refresh the page. If you have the same chat open in app and in browser on mobile they will sync every prompt, but if you prompt on desktop then it will overwrite the conversation branch you've created on the mobile app, but not the mobile browser. In the end it seems that the desktop branch (if created) will always overwrite any others. Fix, just always make sure to refresh your desktop before sending a prompt if you've used the app recently.
github-actions commentedon Dec 20, 2025
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
mynameistito commentedon Dec 21, 2025
issue still exists!disregard didn't realise I was on the wrong account 😅
gwalkerit commentedon Jan 17, 2026
Still an issue, I've had the same chat message in my Claude code mobile app for over 16 hours now.
github-actions commentedon Feb 27, 2026
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
github-actions commentedon Mar 8, 2026
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.