Reliable image viewing from a Windows PC in the Android app

[widingmarcus-cyber]

Use case

I use T3 Code with a Windows PC and the Android app. I want to review images shared or generated in a thread on the PC when I continue that same thread on my phone, without separately hosting or manually transferring the images.

Requested behavior

• Images attached or embedded in the thread are visible on Android.
• Images generated or referenced by the agent on the connected PC have a thumbnail and a tappable larger preview.
• Supported Windows paths work, including paths with spaces and folders such as .t3.
• If an image cannot load, show a useful error and retry action instead of a blank area or an inert link.

Existing work and remaining question

There has already been useful progress:

• fix(media): preview host files and stream videos across clients #9023 merged support for host image/video previews outside the workspace and closed [Bug]: Mobile file links outside the workspace silently do nothing #7798.
• Android host-path Markdown image is blank while desktop and HTTPS embeds work #10322 was closed after a successful retest on a manually built Android 1.0.4. The closure explicitly separated that result from Google Play rollout.
• fix(markdown): keep Windows paths intact in link and image destinations #12615 and fix: render images whose destination has spaces #12815 address Windows path escaping and spaces.
• fix(codex): preview generated images from saved paths #13190 adds previews for Codex-generated images from saved paths.
• Related Ideas: [Feature]: Show Codex Image View results as inline previews on mobile #6947 (mobile Image View previews), [Feature]: ability to preview images in thread #6855 (thread image previews), and Thread-wide navigation for images, media, and file attachments #9609 (thread-wide media navigation).

This is a request to clarify and complete the Windows-to-Android experience, not a claim that the closed bugs still reproduce on the latest build.

Which desktop/server and Google Play app versions should users have for the merged fixes? Is there a tracking plan for the remaining Windows-path and generated-image work, or an existing discussion we should follow?