[BUG] Mobile app shows stale/previous-session messages after using Claude Code on laptop
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
After sending messages and receiving responses in a Claude Code session on my laptop (around 6-7am), I opened the same conversation about an hour later on the mobile app. Instead of showing the morning's conversation and responses, the app displayed messages from the previous night — the morning's exchange was missing/not visible, even though it had completed successfully on the laptop.
What Should Happen?
Opening the same session on a different device (phone) shortly after using it on another device (laptop) should show the current, up-to-date conversation — including messages/responses sent within the last hour — not a stale, older snapshot of the session.
Error Messages/Logs
None visible — no error was shown, the app just silently displayed outdated content.Steps to Reproduce
Use Claude Code (web/cloud session) on a laptop in the morning; send messages and receive responses.
Close the laptop / stop actively using that device.
About an hour later, open the Claude app on a mobile phone and navigate to the same session/conversation.
Observe: the conversation shown reflects the previous night's state, not the messages/responses from that same morning.
Claude Model
Sonnet (default)
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.270
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
This occurred with a persistent session bound to a scheduled daily trigger/routine, if that's relevant — the session continues to receive scheduled automated messages in addition to manual ones, so it's possible the sync issue relates to how the mobile client refreshes sessions that have both manual and scheduled activity. Willing to provide the session ID privately if useful for debugging (not posting it in a public issue).