Linux desktop: ChatGPT/Codex silently exits overnight after internal window teardown, with no crash report

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

Version 26.901.31953

What subscription do you have?

Pro

What platform is your computer?

No response

What issue are you seeing?

Environment

• Ubuntu Linux desktop, GNOME/Wayland
• ChatGPT/Codex Desktop Linux package
• App-reported release: 26.901.20858

What happened

While the workstation remained powered on overnight, the ChatGPT/Codex desktop app silently disappeared. No person interacted with the machine.

Evidence

At 2026-09-04 03:40:00 PDT, the app was healthy immediately beforehand, then recorded:

• both Electron windows as no longer live
• browser session windows removed
• its own app-server transport stopping
• IPC ECONNRESET during cleanup

System evidence for that exact minute shows:

• no reboot, shutdown, logout, sleep, or suspend
• no package update
• no OOM kill, signal, kernel segfault, or coredump
• no audit record of another process terminating ChatGPT/Codex

The app’s systemd scope ended at the same instant.

Expected behavior

The desktop app should remain open while the system remains running, especially during or after long-running tasks. If it must terminate, it should surface a reason and retain a diagnostic crash/lifecycle record.

Actual behavior

All app windows disappeared and the app exited silently. No warning, crash dialog, crash dump, or initiating shutdown reason was recorded.

Notes

The active long-running task had completed earlier; the app continued normal periodic operation until the silent exit.

What steps can reproduce the bug?

Steps to reproduce

Not yet reliably reproducible.

1. Leave the ChatGPT/Codex Linux desktop app running overnight on an otherwise powered-on Ubuntu GNOME/Wayland workstation.
2. In this occurrence, Codex had completed a long-running task earlier in the night.
3. By morning, the app had silently exited.

This has been observed once with the attached timestamped local-log evidence. No user interaction, reboot, suspend, logout, package update, OOM event, or external termination was recorded at the exit time.

What is the expected behavior?

No response

Additional information

No response

Start by examining the Electron window lifecycle, browser session cleanup, app-server transport shutdown, IPC ECONNRESET handling, and the systemd scope behavior described in the report. Reproduce or instrument an overnight run if possible; done means identifying the initiating exit path and preserving a diagnostic lifecycle or crash record when the app terminates silently.