Answer: In the desktop app, open Security, select Scans, and select + Scan, then choose an existing repository or another folder and select Codebase. You can also start a scan from a Codex conversation using $codex-security:security-scan. Status: Confirmed Entry: tool/codex/permissions-and-security/run-security-scan-repository-folder Revision: 2 Digest: sha256:4e9a3be34475b81b (changes whenever the content changes) Timeline: Created: 2026-11-13T03:53:35Z Last changed: 2026-11-18T13:35:50Z (Folder focus example: — → services/billing) Last verified: 2026-11-20T13:42:09Z Next check: 2026-11-21T13:42:09Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Navigation path | Security | [1] | 2026-11-20 Scan button | + Scan | [1] | 2026-11-20 Area selection | Codebase | [1] | 2026-11-20 Conversation command | $codex-security:security-scan | [1] | 2026-11-20 Folder focus example | services/billing | [1] | 2026-11-20 Sources: [1] OpenAI. "Run a Codex Security scan". https://learn.chatgpt.com/docs/security/plugin/scans.md Role: primary. Accessed: 2026-11-20T13:42:09Z Quote: "In the desktop app, open **Security**, select **Scans**, and select **+ Scan**." (Supports: Navigation path) Quote: "select **Scans**, and select **+ Scan**" (Supports: Scan button) Quote: "Choose an existing repository or another folder, then select **Codebase**." (Supports: Area selection) Quote: "Use $codex-security:security-scan to scan this repository for security vulnerabilities." (Supports: Conversation command) Quote: "Use $codex-security:security-scan to scan only services/billing in this repository for security vulnerabilities." (Supports: Folder focus example) Snapshot SHA-256: ff424046a337aedfe922a51cb3a26154934e78606602eb50ad9068b7df296214 (captured 2026-11-17T14:07: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-17T14:07:22Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:42:09Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:42:09Z Last attempt: 2026-11-20T13:42:09Z Notes and limitations: Extracted automatically from a single official source (section "Choose the scan area"). Related: https://latestn.com/tool/codex/permissions-and-security/sandbox-presets What sandbox presets are available in the Codex SDK Python library? https://latestn.com/tool/codex/permissions-and-security/sandbox-restrictions What does the Codex sandbox restrict the agent from doing on my machine? https://latestn.com/tool/codex/permissions-and-security/sandbox-vs-approvals How do sandbox permissions and approval policies work together in Codex? https://latestn.com/tool/codex/permissions-and-security/run-bulk-security-scans How do I run bulk security scans across multiple repositories with Codex Security? https://latestn.com/tool/codex/permissions-and-security/run-first-local-scan How do I run my first local security scan with the Codex Security plugin? https://latestn.com/tool/codex/permissions-and-security/run-propose-security-hardening-workflow How do I run the Codex Security propose-security-hardening workflow? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-18T13:35:50Z | changed | Folder focus example: — → services/billing | [1] 2026-11-18T13:35:50Z | changed | Area selection: — → Codebase | [1] 2026-11-18T13:35:50Z | changed | Scan button: — → + Scan | [1] 2026-11-18T13:35:50Z | changed | Scan type option: Codebase → — | [1] 2026-11-13T03:53:35Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/codex/permissions-and-security/run-security-scan-repository-folder/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/run-security-scan-repository-folder POST: https://latestn.com/dispute/tool/codex/permissions-and-security/run-security-scan-repository-folder with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/codex/permissions-and-security/run-security-scan-repository-folder?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I run a Codex Security scan on a repository or folder? Revision 2, last verified 2026-11-20T13:42:09Z. https://latestn.com/tool/codex/permissions-and-security/run-security-scan-repository-folder (accessed 2026-11-21T10:01:56Z). @misc{LatestN_tool_codex_permissions_and_security_run_security_scan_repository_folder_r2, title = {How do I run a Codex Security scan on a repository or folder?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/codex/permissions-and-security/run-security-scan-repository-folder}}, note = {Revision 2; digest sha256:4e9a3be34475b81b; last verified 2026-11-20T13:42:09Z; accessed 2026-11-21T10:01:56Z} } 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/run-security-scan-repository-folder