Answer: To resume an interrupted bulk scan, run the same bulk-scan command with the original CSV and output directory; Codex Security skips completed repositories. Add `--max-attempts 3` to retry temporary repository or scan errors. Status: Confirmed Entry: tool/codex/commands-and-shortcuts/resume-interrupted-bulk-scan Revision: 2 Digest: sha256:9f95383f3a81bc1a (changes whenever the content changes) Timeline: Created: 2026-11-13T03:53:09Z Last changed: 2026-11-18T13:35:25Z (completed repositories: — → Codex Security skips completed repositories) Last verified: 2026-11-20T13:41:42Z Next check: 2026-11-21T13:41:42Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of resume method | Run the same bulk-scan command with the original CSV and output directory | [1] | 2026-11-20 completed repositories | Codex Security skips completed repositories | [1] | 2026-11-20 retry flag | --max-attempts 3 | [1] | 2026-11-20 Sources: [1] OpenAI. "Codex Security CLI FAQ". https://learn.chatgpt.com/docs/security/cli/faq.md Role: primary. Accessed: 2026-11-20T13:41:42Z Quote: "Run the same bulk-scan command with the original CSV and output directory." (Supports: resume method) Quote: "Codex Security skips completed repositories." (Supports: completed repositories) Quote: "Add `--max-attempts 3` to retry temporary repository or scan errors:" (Supports: retry flag) Snapshot SHA-256: 5e5a9a41f3ff72e7e8c81bebb44325e8de0f2d9f121c768eb9ce4ca932719092 (captured 2026-11-17T14:06:48Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-17T14:06:47Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:41:42Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:41:42Z Last attempt: 2026-11-20T13:41:42Z Notes and limitations: Extracted automatically from a single official source (section "Can an interrupted bulk scan resume"). Related: https://latestn.com/tool/codex/commands-and-shortcuts/run-first-scan How do I run my first Codex Security CLI scan on a local repository? https://latestn.com/tool/codex/commands-and-shortcuts/use-token-with-codex-cli How do I use a Codex access token with Codex CLI? https://latestn.com/tool/codex/features/build-requirement-for-scanning Does a Daybreak Defense Factory project need to be built for scanning? https://latestn.com/tool/codex/commands-and-shortcuts/import-from-cli How do I import scanner findings into Daybreak from the CLI? https://latestn.com/tool/codex/commands-and-shortcuts/open-prompt-editor How do I open an external editor for long prompts in the Codex CLI? https://latestn.com/tool/codex/commands-and-shortcuts/request-codex-review-command How do I request a Codex review on a GitHub pull request? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-18T13:35:25Z | changed | completed repositories: — → Codex Security skips completed repositories | [1] 2026-11-18T13:35:25Z | changed | completed scans retry behavior: Completed scans keep their results and aren't retried → — | [1] 2026-11-18T13:35:25Z | changed | workers: --workers 4 → — | [1] 2026-11-18T13:35:25Z | changed | completed repositories behavior: Codex Security skips completed repositories. → — | [1] 2026-11-18T13:35:25Z | changed | resume method: Run the same bulk-scan command with the original CSV and output directory. → Run the same bulk-scan command with the original CSV and output directory | [1] 2026-11-13T03:53:09Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/codex/commands-and-shortcuts/resume-interrupted-bulk-scan/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/codex/commands-and-shortcuts/resume-interrupted-bulk-scan POST: https://latestn.com/dispute/tool/codex/commands-and-shortcuts/resume-interrupted-bulk-scan with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/codex/commands-and-shortcuts/resume-interrupted-bulk-scan?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I resume an interrupted bulk scan in Codex Security CLI? Revision 2, last verified 2026-11-20T13:41:42Z. https://latestn.com/tool/codex/commands-and-shortcuts/resume-interrupted-bulk-scan (accessed 2026-11-21T10:04:24Z). @misc{LatestN_tool_codex_commands_and_shortcuts_resume_interrupted_bulk_scan_r2, title = {How do I resume an interrupted bulk scan in Codex Security CLI?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/codex/commands-and-shortcuts/resume-interrupted-bulk-scan}}, note = {Revision 2; digest sha256:9f95383f3a81bc1a; last verified 2026-11-20T13:41:42Z; accessed 2026-11-21T10:04:24Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/codex/commands-and-shortcuts/resume-interrupted-bulk-scan