codex - 💡(How to fix) Fix rollout file not written until first API turn completes, no way to get thread_id at spawn time for embedding tools

TL;DR

Implementing a solution to write session_meta to the rollout file at session initialization or adding support for a --session-id flag could resolve the issue of correlating external tool session identifiers with Codex thread IDs.

Guidance

• To address the problem, consider modifying the Codex session initialization process to write the session_meta to the rollout file immediately, rather than waiting for the first API turn to complete.
• Alternatively, explore adding a --session-id flag that allows external tools to assign a session ID, which could then be used to correlate with the Codex thread ID.
• Investigate the feasibility of using environment variables or other signals to expose the session ID to the host process earlier in the session lifecycle.
• Review related issues (#15767, #8923, #15870) for potential insights or existing solutions that could be adapted to this problem.

Example

No specific code example is provided due to the lack of detailed implementation context, but the solution might involve modifying the Codex initialization code to write to the rollout file sooner or adding a new command-line flag for custom session ID assignment.

Notes

The exact implementation details will depend on the internal workings of Codex and its session management mechanisms, which are not fully described in the issue. Therefore, any solution will need to be tailored to the specific requirements and constraints of the Codex system.

Recommendation

Apply a workaround by modifying the Codex session initialization to write the session_meta to the rollout file at the start, as this directly addresses the root cause of the delay in correlating session identifiers.