[BUG] iOS Claude Code - unsent prompt lost when swiping left out of the session
Status Open
Reported on v2.1.158
Maintainer reply None cached
Activity 4 comments · opened May 30, 2026
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?
On remote control sessions, if I type anything or multiple paragraphs, then I swipe left to go back to the list of sessions, the prompt is no longer there when i go back.
Especially painful when editing detailed prompts and accidental swipe gesture is detected while selecting text.
What Should Happen?
Draft should persist or warn before dismissal
Error Messages/Logs
Steps to Reproduce
- open a claude code session on mobile
- type a prompt, dont send it
- swipe left to go back to list of code sessions
- re enter the chat, your prompt is gone
Claude Model
Not sure / Multiple models
Is this a regression?
No, this never worked
Last Working Version
_No response_
Claude Code Version
2.1.158
Platform
Anthropic API
Operating System
Other
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
4 Comments
+1
Just spent half an hour writing a very detailed customer journey prompt and lost it in half a second. Very painful... 😖
[Claude] Reproduces on Android, and in my case the lost message had already been queued, which may make it a distinct defect from the one described here.
Platform. Same behavior in a Remote Control session on Android, so this is not iOS-specific —
platform:androidprobably belongs alongsideplatform:ios.**Backgrounding does not lose it.** Pulling down the notification shade, or switching to another app and returning, both preserve the text. Only navigating away from the session inside the app loses it.
It was a queued message, not composer text. The session was mid-turn, and typing while it was busy put the message into a visible queued state — accepted, not an unsent draft. Leaving the session dropped that queued message with no warning and no trace in the transcript. That is worse than losing typed-but-unsent text: the queued state tells you the message will be delivered, so there is no reason to return and check.
If this issue is specifically about text still sitting in the composer, the queued case may deserve splitting out. Both share the trigger, but the fixes differ.
Fix. Preserving the composer draft across in-app navigation covers the unsent case. It does not cover this one. A queued message has to be held by the remote-controlled session itself, so that closing the screen, unloading the app, or losing the phone entirely still leaves the message to be delivered on the session's next turn — the same as input typed into that session locally. #71603 describes the queued-message behavior wanted on the Claude Code on the web surface.
How on earth is this not fixed AND a standard feature in September of 2026? Imagine if your half-written text message vanished because you fat-fingered a nearby text in the menu, then tapped back and it was gone?
This needs to be a priority fix. Codex/ChatGPT figured it out.
I don't have to imagine it...