codex - 💡(How to fix) Fix premature close [1 comments, 2 participants]

TL;DR

Resuming an instance with "codex e 'prompt' resume <uuid>" may not maintain the terminal session's position in messages as expected.

Guidance

• Verify that the issue is specific to resuming an instance with the given command and not a general problem with the Codex API.
• Check if the UUID is correctly passed and recognized when resuming the instance.
• Test resuming the instance without forking to see if the terminal session's position is maintained.
• Consider providing more details about the script and the environment used for reproduction to help identify the cause.

Notes

The issue seems to be related to the behavior of the Codex API when resuming an instance, but more information is needed to determine the root cause.

Recommendation

Apply workaround: Modify the script to handle the instance resumption differently, potentially by re-fetching the message position after resuming, as the current behavior may not be supported by the Codex API.