Conversation interrupted when terminal lost connection

What version of Codex CLI is running?

codex-cli 0.153.4

What subscription do you have?

PRO (20x)

Which model were you using?

GPT-5.6 xhigh

What platform is your computer?

Linux 7.0.0-31-generic x86_64 unknown

What terminal emulator and version are you using (if applicable)?

Several on iPhone and macOS Terminal

Codex doctor report

What issue are you seeing?

For about two days now—specifically, a few days after the release of GPT-6 ASTRA or following a CLI update (around update 0.153.3), and possibly linked to issue #37552—I have been experiencing an issue where the CLI suddenly aborts whenever I lose the connection to my only terminal (e.g., due to a network outage or unexpected disconnection). This happens up to 20 times a day, and I don't realize the agent has stopped working until I manually reconnect.

This is a serious problem, as I am constantly worried that the agent won't be able to work because I can currently only use one terminal (due to #37552).

It does not work after that.

What steps can reproduce the bug?

Use a single connection (terminal) and abort the connection to check if the agent continous

What is the expected behavior?

No response

Additional information

No response

No source file, test, or entry point is named. Start by reproducing the failure with Codex CLI 0.153.4 using a single terminal connection, then trace how terminal disconnection is handled; done means the agent does not abort when that connection is lost and can continue or recover as intended.