Android Remote image attachments are not routed as active-turn steering

What version of the Codex app are you using?

Android Codex 1.2026.209, installed from Google Play.

Windows Desktop host: Windows 10 x64.

What issue are you seeing?

When a Codex task has an active assistant turn and I open that same task through Remote on Android, an image-bearing message is not delivered as steering/addendum input to the active turn.

The attachment may surface only after the active turn has ended or paused, as a separate ordinary user turn, rather than modifying the in-progress turn. Text-only steering and image-bearing submissions appear to take different routing paths.

In the observed reproduction, the supporting screenshots could not be sent from mobile at the time of failure. I had to wait until I returned home and upload them from the Windows desktop. Their eventual appearance in the task is therefore not evidence that mobile image steering succeeded.

Steps to reproduce

1. Start a Codex task on a Windows Desktop host and leave its assistant turn running.
2. Open that same task through Remote on Android.
3. Attach an image/photo, optionally add text, and send it while the assistant turn is active.
4. Observe that the active turn does not receive the image as a steering/addendum message.

Expected behavior

An image-bearing mobile message should either:

• steer the currently active turn atomically with its accompanying text; or
• be explicitly queued/refused with a visible status explaining that it will become the next turn.

It should not silently miss the active turn or change from a steer into a later standalone message.

Why this matters

Screenshots are often the fastest way to correct a UI-control task. If mobile image submissions are not delivered to the active turn, the agent can continue acting on stale visual information while the user believes the correction was received.

Additional environment details

• Connection during the captured reproduction: 4G cellular.
• Android App info reported 122 MB of internal storage used by Codex and 350 MB of mobile data used since June 1.
• Observed on 2026-08-09.
• A separate large-task hydration failure occurred concurrently, but this report is specifically about image-bearing messages not being routed as active-turn steering.

No account identifiers, task IDs, local paths, or image contents are included.