Answer: False-positive feedback works by recording why a finding doesn't apply using the findings false-positive command with a --reason; future scans of the same repository receive that explanation as context but still independently check the current source, controls, and reachability, and a dismissal doesn't suppress a rule, path, or vulnerability class. Status: Confirmed Entry: tool/codex/features/false-positive-feedback Revision: 2 Digest: sha256:69117670856f3b70 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:53:10Z Last changed: 2026-11-18T13:35:26Z (dismissal scope: A dismissal doesn't suppress a rule, path, or vulnerability class. → A dismissal doesn't suppress a rule, path, or vulnerability class.) 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 command | npx @openai/codex-security findings false-positive FINDING_OCCURRENCE_ID | [1] | 2026-11-20 reason flag | --reason | [1] | 2026-11-20 future scan behavior | Future scans of the same repository receive that explanation as context. | [1] | 2026-11-20 independent checks | They still independently check the current source, controls, and reachability. | [1] | 2026-11-20 dismissal scope | A dismissal doesn't suppress a rule, path, or vulnerability class. | [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: "npx @openai/codex-security findings false-positive FINDING_OCCURRENCE_ID" (Supports: command) Quote: "--reason "The framework escapes this input before it reaches the query"" (Supports: reason flag) Quote: "Future scans of the same repository receive that explanation as context." (Supports: future scan behavior) Quote: "They still independently check the current source, controls, and reachability." (Supports: independent checks) Quote: "A dismissal doesn't suppress a rule, path, or vulnerability class." (Supports: dismissal scope) 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:48Z, 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 "How does false-positive feedback work"). Related: https://latestn.com/tool/codex/features/find-reviews-needing-attention How do I find Codex code reviews that need attention? https://latestn.com/tool/codex/features/first-scan-baseline How do I use my first Codex Security scan as a baseline? https://latestn.com/tool/codex/features/follow-scan-progress How do I follow the progress of a Codex Security scan? https://latestn.com/tool/codex/features/default-universal-image What is the default universal image used in Codex Cloud environments? https://latestn.com/tool/codex/features/enable-feature-flags How do I enable feature flags in Codex? https://latestn.com/tool/codex/features/enable-otel-monitoring How do I enable OpenTelemetry (OTel) monitoring for Codex? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-18T13:35:26Z | changed | dismissal scope: A dismissal doesn't suppress a rule, path, or vulnerability class. → A dismissal doesn't suppress a rule, path, or vulnerability class. | [1] 2026-11-18T13:35:26Z | changed | independent checks: They still independently check the current source, controls, and reachability. → They still independently check the current source, controls, and reachability. | [1] 2026-11-13T03:53:10Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/codex/features/false-positive-feedback/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/features/false-positive-feedback POST: https://latestn.com/dispute/tool/codex/features/false-positive-feedback with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/codex/features/false-positive-feedback?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How does false-positive feedback work in Codex Security CLI? Revision 2, last verified 2026-11-20T13:41:42Z. https://latestn.com/tool/codex/features/false-positive-feedback (accessed 2026-11-21T09:53:17Z). @misc{LatestN_tool_codex_features_false_positive_feedback_r2, title = {How does false-positive feedback work in Codex Security CLI?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/codex/features/false-positive-feedback}}, note = {Revision 2; digest sha256:69117670856f3b70; last verified 2026-11-20T13:41:42Z; accessed 2026-11-21T09:53:17Z} } 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/features/false-positive-feedback