Remote mobile Codex does not render local media artifacts linked from assistant messages

[NateSpencerWx]

What version of the Codex App are you using (From “About Codex” dialog)?

Codex App 26.527.3686.0 on Windows host; ChatGPT iOS app 1.2026.132 (26051406691); ChatGPT Desktop package 1.2026.133.0 also installed.

What subscription do you have?

Plus

What platform is your computer?

Windows 11 Pro 10.0.26200 x64 host, accessed from ChatGPT mobile Codex remote control.

What issue are you seeing?

Using Codex from the ChatGPT mobile app remote-control view, generated local media artifacts referenced by assistant Markdown do not render on mobile. The desktop host successfully created PNG/GIF/MP4 files in the workspace, and the Codex session continued to work for commands, text updates, and normal conversation. However, when the assistant tagged those artifacts in messages using local paths such as C:/Users//project/artifacts/demo.png or demo.mp4, the mobile app did not load the media. This made it impossible for the mobile user to preview generated screenshots/video even though everything else in the remote Codex session was working.

What steps can reproduce the bug?

1. Connect to a desktop Codex session from the ChatGPT mobile app remote Codex view.
2. Ask Codex to create a visual artifact in the workspace, such as a PNG, GIF, or MP4.
3. Have the assistant reference the artifact in the conversation with Markdown, for example , or an MP4/GIF under the same workspace.
4. View the thread from ChatGPT mobile Codex.

In my repro, text messages and command output rendered, and the files existed on the host, but the tagged media did not load in the mobile view.

What is the expected behavior?

The mobile remote Codex view should either render generated local media artifacts from assistant messages, or expose them as relay-backed/openable attachments. If Markdown links to local workspace files are intentionally unsupported, the UI or assistant tooling should make that clear so assistants do not present broken media tags to mobile users.

Additional information

This appears to be a media delivery/rendering issue, not a Codex execution issue. The CLI/demo artifacts were successfully generated on the Windows host. Text updates, command output, and normal Codex interaction continued to work from mobile. I searched before filing; related but not exact issues include #14576, #12439, and #23062.

[Snailflyer]

This needs an artifact transport contract, not just better Markdown rendering.

A local path like C:/Users/.../demo.png is useful on the host but ambiguous on mobile. I would expect Codex to translate generated local media into an artifact record with fields like:

• artifact id
• host id
• workspace or project root
• original host path hash, not necessarily the raw path
• mime type
• byte size
• created-by session id / turn id
• process generation
• availability: relay-ready, host-only, expired, or blocked-by-policy
• preview URL or explicit unavailable reason

Then the mobile UI can show either a relay-backed preview/download or a clear host-only artifact state. A broken image tag makes the user think Codex failed to create the file, when the real failure is that the mobile projection cannot dereference a host-local path.

This is a close cousin of the same-session proof problem I have been working on in Faryo. For mobile workbenches, "assistant referenced the file" is not enough; the receiving surface needs proof that the artifact is reachable from the same live host/session:
https://github.com/Snailflyer/faryo