Android Codex Remote loses drafted voice/text input on connection interruptions and requires full reconnect

What issue are you seeing?

ChatGPT for Android handles temporary connection problems much better in normal ChatGPT chats than in Codex Remote / Work mode.

In normal ChatGPT chats:

• If the connection is temporarily lost, for example in an elevator or on weak mobile internet, the app usually keeps the drafted text or voice transcription.
• There is a visible retry / refresh / reconnect behavior.
• The user can continue and send the message after connection is restored.

In Codex Remote / Work mode:

• The connection is much less stable.
• Temporary network loss often breaks the Remote session.
• The app shows connection errors and requires reconnecting.
• Sometimes the whole input area disappears.
• After that, I cannot even type text into the Remote thread.
• A long dictated message can simply disappear.
• The only practical fix is often to restart/reopen the app and reconnect to the Remote session.
• This makes mobile Remote usage very unreliable.

Steps to reproduce:

1. Open ChatGPT for Android.
2. Open an existing Codex Remote / Work session connected to a desktop.
3. Start typing or dictating a long prompt.
4. Move through an area with weak mobile internet, switch networks, go through an elevator, or briefly background/foreground the app.
5. Return to the Codex Remote session.

Actual result:
The Remote connection often breaks. The input field may disappear or become unusable. The drafted/dictated message can be lost. The user has to reconnect or restart the app.

Expected result:
Codex Remote on Android should handle connection interruptions at least as reliably as normal ChatGPT chats.

Expected behavior:

• Preserve the current draft text.
• Preserve voice transcription text if it was already recognized.
• Never silently delete the user's input.
• Show a clear reconnect/retry button.
• Automatically resume the Remote connection when internet returns.
• Keep the input box usable even when the Remote connection is temporarily interrupted.
• Do not require full app restart for ordinary connection loss.

Why this matters:
Remote usage from Android often happens on mobile internet. Short connection interruptions are normal. Losing a long dictated technical prompt is extremely frustrating and makes Codex Remote unreliable for real work.

This looks especially bad because the same ChatGPT Android app handles connection loss much better in normal chats, but Codex Remote behaves much worse.

Please reuse or bring the normal ChatGPT draft preservation and reconnect behavior into Android Codex Remote.

What steps can reproduce the bug?

1. Open ChatGPT for Android.
2. Open an existing Codex Remote / Work session connected to a desktop.
3. Start typing or dictating a long prompt.
4. Move through weak mobile internet, switch networks, go through an elevator, or briefly background/foreground the app.
5. Return to the Codex Remote session.

What is the expected behavior?

Codex Remote on Android should preserve draft and recognized voice text, keep the input usable, show a clear reconnect/retry path, and resume after ordinary mobile connection interruptions.

Additional information

_No response_