Answer: To run your first Codex Security scan on a local repository, select Security in the sidebar, open Scans, and select + Scan; then choose the codebase and scan area, add security context, and select Start scan. For best scan quality, use gpt-5.6-sol with xhigh reasoning effort. Status: Confirmed Entry: tool/codex/features/run-first-security-scan Revision: 1 Digest: sha256:e36919ae7e79e450 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:53:23Z Last changed: 2026-11-13T03:53:23Z Last verified: 2026-11-20T13:41:56Z Next check: 2026-11-21T13:41:56Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of recommended model | gpt-5.6-sol | [1] | 2026-11-20 recommended reasoning effort | xhigh | [1] | 2026-11-20 first setup step | Security | [1] | 2026-11-20 scan area option | Codebase | [1] | 2026-11-20 deep scan setting | Deep scan | [1] | 2026-11-20 start action | Start scan | [1] | 2026-11-20 CLI prompt | Run a Codex Security scan on this repository. | [1] | 2026-11-20 report file | report.md | [1] | 2026-11-20 Sources: [1] OpenAI. "Codex Security plugin quickstart". https://learn.chatgpt.com/docs/security/plugin.md Role: primary. Accessed: 2026-11-20T13:41:56Z Quote: "For the best scan quality, use `gpt-5.6-sol`" (Supports: recommended model) Quote: "with `xhigh` reasoning effort." (Supports: recommended reasoning effort) Quote: "Select **Security** in the sidebar, open **Scans**, and select **+ Scan**." (Supports: first setup step) Quote: "Choose **Codebase**," (Supports: scan area option) Quote: "leave **Deep scan** off, and select the entire repository or one folder." (Supports: deep scan setting) Quote: "Select **Start scan** and follow the scan phases in the Security workbench." (Supports: start action) Quote: "Run a Codex Security scan on this repository." (Supports: CLI prompt) Quote: "open the generated `report.md` for" (Supports: report file) Snapshot SHA-256: 4e34ccf951a9d5f02cc40f4b38ebd99595ed6dfe8970938365b50d9cb0d96826 (captured 2026-11-13T03:53:23Z) 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:23Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:41:56Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:41:56Z Last attempt: 2026-11-20T13:41:56Z Notes and limitations: Extracted automatically from a single official source (section "Run your first scan"). Related: https://latestn.com/tool/codex/features/scan-local-checkout How do I scan my local checkout with Daybreak Defense Factory? https://latestn.com/tool/codex/features/security-scan-output What does a Codex Security scan create and does it modify my source code? https://latestn.com/tool/codex/features/share-codex-thread-snapshot How do I share a read-only snapshot of a Codex thread? https://latestn.com/tool/codex/features/reopen-previous-scan How do I reopen a previous Codex Security scan? https://latestn.com/tool/codex/features/reusable-cloud-environments How do I prepare reusable Codex Cloud environments? https://latestn.com/tool/codex/features/review-changes-in-ide How do I review and keep Codex edits beside my code in the IDE? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:53:23Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/codex/features/run-first-security-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/features/run-first-security-scan POST: https://latestn.com/dispute/tool/codex/features/run-first-security-scan with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/codex/features/run-first-security-scan?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I run my first Codex Security scan on a local repository? Revision 1, last verified 2026-11-20T13:41:56Z. https://latestn.com/tool/codex/features/run-first-security-scan (accessed 2026-11-21T09:53:18Z). @misc{LatestN_tool_codex_features_run_first_security_scan_r1, title = {How do I run my first Codex Security scan on a local repository?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/codex/features/run-first-security-scan}}, note = {Revision 1; digest sha256:e36919ae7e79e450; last verified 2026-11-20T13:41:56Z; accessed 2026-11-21T09:53:18Z} } 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/run-first-security-scan