Playbooks · Coding tasks
Codex Security 0.10.0: resume a scan, cap a batch
Written November 14, 2026
0.10.0 lets an interrupted scan resume, puts one budget over a batch of repos, and explains a blocked patch instead of failing quietly.
What changed
Codex Security 0.10.0, published November 12, is an operating release rather than a detection release. Its own summary names three changes: clearer guidance when a patch is blocked, a way to resume interrupted Standard scans, and a budget for batch scans. For anyone who ran the scanner after the intro page and watched a long scan die partway through, the resume command is the change that matters most. The batch budget runs a close second for teams scanning more than one repository.
Resume an interrupted scan
Run codex-security scans resume SCAN_ID to continue an interrupted Standard scan from a saved checkpoint in the original Codex session. The resumed scan retains its usage and its budget, so a resume does not reset what the scan has already spent. That detail changes how a failure is handled in practice. Before 0.10.0, an interrupted scan meant starting the audit again and paying for the repeated work. Now the first move after an interruption is to resume with the scan's ID and let the checkpoint carry the state. The notes also record, under standard scan setup, that scan history now records the file count from the scan's inventory, which gives a resumed run a clearer record of what the original pass covered.
One budget over a batch
Set --max-total-cost on bulk or component scans to share one estimated budget across repositories or components. The budget covers retries and recoveries as well as the scans themselves, so a flaky run that restarts work still draws from the same pot instead of opening a new one. One caveat travels with the flag, stated in the notes in plain terms: in-flight work can exceed the estimate. Treat the number as a ceiling on planned spend, not a hard stop that lands exactly on the figure. A batch already running when the budget runs out can finish above it.
Budgets interact with patch work in one specific way. When a scan has a cost limit, run patch preparation separately: the notes say a scan with a budget rejects an explicit patch follow-up and skips its interactive patch offer. Plan the patch step as its own run rather than expecting the scan to offer it at the end.
Blocked patches explain themselves
When a patch cannot be applied, the result now says more than that it failed. The patch prompt asks whether any files changed, what stopped the fix, and what to do next. When a fix depends on work outside the checkout, the result explains why that external change is needed and, where the release puts it, where the change belongs. For hosted remediation there is a related change: a hosted patch or verification that ends at a different commit reports revision_changed and retains its execution receipt, and the instruction is to retry from the requested revision. A blocked patch is now a task with a stated next step, instead of a dead end that a maintainer has to reverse-engineer from a log.
Imports and publication
Two smaller additions round out the release. Saved ArmorCode SAST findings can be imported into the local workbench, so findings from an existing SAST run can sit alongside the scanner's own results. And SDK callers can publish selected workbench finding versions to Cloud using retained evidence, which moves a chosen finding out of the local workbench without publishing everything in it.
What to do
Update to 0.10.0 before your next long scan, and keep scan IDs: resume now depends on having the ID of the interrupted scan. For any bulk or component run, set --max-total-cost up front and leave headroom for the in-flight overshoot the notes describe. If a patch comes back blocked, read the stated blocker before rerunning anything — the result now names the external change or the next step, and a blind rerun will hit the same wall.
Related playbooks
- Codex Security scans a repo and patches it
- Queue a Codex message and resume the thread
- Foundry retires codex-mini on November 15
- ChatGPT and Codex share one token budget
Sources
Back to: Coding playbooks hub · Also: Codex Security scans a repo and patches it · Copilot CLI 1.0.112: the November 13 build