chore(cli): explain why deep scans stop - #577
Open
ianw-oai wants to merge 1 commit into
Open
Conversation
ianw-oai
changed the title
ianw-oai
marked this pull request as ready for review
August 20, 2026 05:14
Collaborator
Author
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The CLI does not explain why a deep scan stopped. A user can mistake a scan limit for a complete review. Show the stop reason in plain language and explain how to scan further when a limit was reached.
Changes
Read the existing saved scan status and add a
STOPPEDline to the CLI summary. Distinguish review limits, time limits, cost limits, and repeated reviews that found no new issues. Show whether the latest review still found new issues. A failure to read this extra status does not fail a completed scan.Testing
pnpm run test --seed 12345: 1,446 passed, 23 skipped, zero failures.pnpm run test: 1,446 passed, 23 skipped, zero failures.pnpm run types: passed.pnpm run format: passed.git diff --check: passed.Risk and rollout
This changes CLI text only. It does not change scan limits, standard scan output, saved reports, JSON output, or exit codes. No database change or rollout flag is required.
Public disclosure review