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
Claude Code remote control iOS app (mobile companion app).
Summary
While the agent is busy processing a turn, a prompt entered into the composer — a message that has not yet been consumed by an LLM turn — is held only in the in-memory chat view. If you navigate away from the session (to another session, or back to the session list) and return, that pending prompt is silently discarded. It is not persisted across the app's navigation.
This is a functional / data-loss problem, not just a cosmetic UI glitch: the queued prompt is often a long, carefully-composed message, and losing it silently can wipe out a lot of context and significantly degrade the experience.
Steps to Reproduce
Open a session where the agent is actively working on a task (busy / mid-turn).
Enter a prompt into the composer. It stays visible in the chat as a pending/queued prompt — not yet consumed by an LLM turn.
Navigate away — either open a different session, or go back to the session list.
Return to the original session.
Expected Behavior
The pending, unsent prompt is still present when you return, ready to be consumed by the next turn. Queued input should survive in-app navigation just like it survives waiting for the current turn to finish.
Actual Behavior
The pending prompt is gone. It was only held in the chat view and is not preserved across navigation, so it is silently lost on return — with no warning and no way to recover it.
Impact
This is a functional data-loss bug, not merely a UI issue. Any prompt queued while the agent is busy is lost the moment you briefly leave the session (or glance at another one), forcing the user to retype it from scratch. Queued prompts are frequently long and context-rich — losing one can mean losing a significant amount of carefully-composed input with no warning and no way to recover it, which materially degrades the user experience.
Environment
App: Claude Code remote control (iOS)
OS: iOS
Trigger: Navigating away from a session (to another session or the session list) and back, while a prompt is queued/unsent.
Platform
Claude Code remote control iOS app (mobile companion app).
Summary
While the agent is busy processing a turn, a prompt entered into the composer — a message that has not yet been consumed by an LLM turn — is held only in the in-memory chat view. If you navigate away from the session (to another session, or back to the session list) and return, that pending prompt is silently discarded. It is not persisted across the app's navigation.
This is a functional / data-loss problem, not just a cosmetic UI glitch: the queued prompt is often a long, carefully-composed message, and losing it silently can wipe out a lot of context and significantly degrade the experience.
Steps to Reproduce
Expected Behavior
The pending, unsent prompt is still present when you return, ready to be consumed by the next turn. Queued input should survive in-app navigation just like it survives waiting for the current turn to finish.
Actual Behavior
The pending prompt is gone. It was only held in the chat view and is not preserved across navigation, so it is silently lost on return — with no warning and no way to recover it.
Impact
This is a functional data-loss bug, not merely a UI issue. Any prompt queued while the agent is busy is lost the moment you briefly leave the session (or glance at another one), forcing the user to retype it from scratch. Queued prompts are frequently long and context-rich — losing one can mean losing a significant amount of carefully-composed input with no warning and no way to recover it, which materially degrades the user experience.
Environment
Attachments
ScreenRecording_07-02-2026.09-56-55_1.mp4