Android Remote: generated output fails to open with `Slingshot app-server connection invalidated`

<img width="852" height="1846" alt="Redacted Android Remote Slingshot file-open error" src="https://github.com/user-attachments/assets/48df23ac-bfb6-445d-949d-479afd0d5b4d" />

What version of the Codex App are you using?

• Codex Desktop package: 26.818.8289.0
• ChatGPT Android app: last verified installed version 1.2026.209 (not rechecked during this exact tap)
• Host: Windows 10 Home 22H2 x64, build 19045.7663

What issue are you seeing?

In an existing Codex Remote task on Android, tapping a generated local output link failed with:

Couldn't open file

Slingshot app-server connection invalidated.

The task itself was visible and hydrated, the final response was present, and both generated-file links were clickable. The failure occurred only when opening the PDF.

The referenced PDF still existed normally on the Windows host and was readable locally (579,993 bytes). The paired PNG also existed. This was therefore not a missing-output-file failure.

Steps to reproduce

1. Open an existing Windows-hosted Codex task through Remote in the ChatGPT Android app.
2. Let the task create a PDF or another output file under its local outputs directory.
3. Wait for the final response containing the local file link.
4. Tap the PDF link on Android.
5. Observe the file-open sheet fail with Slingshot app-server connection invalidated.

Host-side timing evidence

The failure was captured at approximately 2026-08-27 07:13 UTC.

In the exact surrounding window, the Windows desktop log showed the active task continuing normally. A normal app-server response was routed at 07:14:16 UTC, and there was no app-server disconnect, restart, or exit event around 07:12–07:14 UTC.

This suggests the invalidated object is likely a Remote/Slingshot file-opening route or connection generation, not the sole local app-server process itself. That is an inference, not a confirmed root cause.

Expected behavior

Tapping a generated local output link through Remote should open or download the file while the Windows host and task remain connected. If the file bridge has gone stale, Remote should transparently rebind it or offer a retry that does not require restarting the task or desktop app.

Actual behavior

The file exists and the task remains usable, but the file opener rejects the request because its Slingshot app-server connection has been invalidated.

Related reports

This may share host-alias or route-lifecycle mechanics with #35394 and #36404, but neither report covers opening an existing local output from Android Remote.

Privacy

The attached screenshot has the host name, username, absolute path, task identifiers, and prompt-derived directory names redacted.