Answer: In the desktop app, open Security, select Scans, and select + Scan, then choose the repository and select Changes to review uncommitted changes, a single commit, or a base and head revision. You can also ask Codex in a conversation to use $codex-security:security-diff-scan to review uncommitted changes or a commit/branch range. Status: Confirmed Entry: tool/codex/permissions-and-security/manual-security-review-of-changes Revision: 1 Digest: sha256:fdb8dca06414de63 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:53:24Z Last changed: 2026-11-13T03:53:24Z Last verified: 2026-11-20T13:41:58Z Next check: 2026-11-21T13:41:58Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Navigation path | Security | [1] | 2026-11-20 Scan type option | Changes | [1] | 2026-11-20 Reviewable scopes | uncommitted changes, a single commit, or a base and head revision | [1] | 2026-11-20 Deep scan availability | Deep scan | [1] | 2026-11-20 Conversation command | $codex-security:security-diff-scan | [1] | 2026-11-20 Sources: [1] OpenAI. "Review code changes for security". https://learn.chatgpt.com/docs/security/plugin/code-changes.md Role: primary. Accessed: 2026-11-20T13:41:58Z Quote: "In the desktop app, open **Security**, select **Scans**, and select **+ Scan**." (Supports: Navigation path) Quote: "Choose the repository, then select **Changes**." (Supports: Scan type option) Quote: "Review uncommitted changes, a single commit, or a base and head revision." (Supports: Reviewable scopes) Quote: "**Deep scan** isn't available for a changes scan." (Supports: Deep scan availability) Quote: "Use $codex-security:security-diff-scan to review my current uncommitted changes for security regressions." (Supports: Conversation command) Snapshot SHA-256: 7234ef879ffd798a3ef2b034996d0776d9aa39c27bb78e81c2a2293862b4559c (captured 2026-11-13T03:53:25Z) 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-13T03:53:24Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:41:58Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:41:58Z Last attempt: 2026-11-20T13:41:58Z Notes and limitations: Extracted automatically from a single official source (section "Run a manual review"). Related: https://latestn.com/tool/codex/permissions-and-security/migrate-sandbox-to-profiles How do I migrate Codex from older sandbox settings to permission profiles? https://latestn.com/tool/codex/permissions-and-security/migrate-untrusted-approval-policy How do I migrate from the retired untrusted approval policy in Codex? https://latestn.com/tool/codex/permissions-and-security/permission-modes-overview What permission modes does ChatGPT and Codex offer for local actions? https://latestn.com/tool/codex/permissions-and-security/inspect-repository-history How do I inspect repository history in the Codex Security workbench? https://latestn.com/tool/codex/permissions-and-security/isolate-environment-cybersecurity How do I isolate the environment when running Codex for cybersecurity work? https://latestn.com/tool/codex/permissions-and-security/manage-privileges How do I manage privileges and permissions for the Codex GitHub Action? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:53:24Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/codex/permissions-and-security/manual-security-review-of-changes/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/permissions-and-security/manual-security-review-of-changes POST: https://latestn.com/dispute/tool/codex/permissions-and-security/manual-security-review-of-changes with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/codex/permissions-and-security/manual-security-review-of-changes?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I run a manual security review of code changes in Codex? Revision 1, last verified 2026-11-20T13:41:58Z. https://latestn.com/tool/codex/permissions-and-security/manual-security-review-of-changes (accessed 2026-11-21T10:05:03Z). @misc{LatestN_tool_codex_permissions_and_security_manual_security_review_of_changes_r1, title = {How do I run a manual security review of code changes in Codex?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/codex/permissions-and-security/manual-security-review-of-changes}}, note = {Revision 1; digest sha256:fdb8dca06414de63; last verified 2026-11-20T13:41:58Z; accessed 2026-11-21T10:05:03Z} } 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/permissions-and-security/manual-security-review-of-changes