Summary
codex-security creates standard Codex rollout sessions for coordinators and workers, but scan results do not identify those sessions or provide a way for external trace tools to index them. This is an issue particularly when a scan fails.
Problem
A scan ran for ~3 hours and unexpectedly failed before producing a report. Its private Codex home still contained 87 valid rollout files, including parent metadata for all 56 child sessions.
Recovering them required manually correlating timestamps, temporary working directories, and session metadata. The scan record did not expose their location or IDs.
Requested workflow
Allow users and local observability tools to retain and index the coordinator and worker traces associated with a scan, especially when the scan fails.
Summary
codex-security creates standard Codex rollout sessions for coordinators and workers, but scan results do not identify those sessions or provide a way for external trace tools to index them. This is an issue particularly when a scan fails.
Problem
A scan ran for ~3 hours and unexpectedly failed before producing a report. Its private Codex home still contained 87 valid rollout files, including parent metadata for all 56 child sessions.
Recovering them required manually correlating timestamps, temporary working directories, and session metadata. The scan record did not expose their location or IDs.
Requested workflow
Allow users and local observability tools to retain and index the coordinator and worker traces associated with a scan, especially when the scan fails.