openai / openai/codex-security
Expose a scan-session artifact index and optional rollout export
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 10.8k
- Forks
- 801
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 257
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how a scan records its result and how coordinator and worker rollout files are retained in the private Codex home. Use the reported failure case—87 rollout files, parent metadata, and 56 child sessions—to define the artifact index and optional export scope. Done means external trace tools can identify and retain the associated sessions even when a scan fails.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- cli, observability, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100