codex - 💡(How to fix) Fix Subagent resume [2 comments, 3 participants]

TL;DR

Retaining subagent rollout history during session resumption may require modifications to the Codex CLI's session management or data storage mechanisms.

Guidance

• Investigate the Codex CLI's current session management and data storage approaches to understand how subagent information is handled.
• Consider implementing a data persistence mechanism to store subagent rollout history, allowing it to be retrieved when a session is resumed.
• Review the Codex CLI's documentation and existing features to see if there are any configuration options or workarounds that can help retain subagent information during session resumption.
• If direct resumption of subagent threads is not currently possible, explore alternative approaches, such as re-creating the subagent thread with its previous state.

Notes

The exact implementation details will depend on the internal workings of the Codex CLI, which are not provided in the issue description.

Recommendation

Apply workaround: Implement a custom data persistence mechanism to store subagent rollout history, as the current Codex CLI functionality may not support this feature.