Creator Digest
OOpenAI· 2.1M subscribers

How to run your first Codex Security scan

7 min videoNov 11, 2026Worth watching in full

Install the Codex Security plugin, scan a repository with focused additional context, review findings and fixes, then use the CLI to automate scans.

  • Confirm Daybreak Blue access, install the Codex Security plugin, and select a repository and model for a scan.
  • Enable additional context to focus the analysis—for example, on the application’s authentication service.
  • Review the vulnerability and proposed patch before publishing a pull request; use the CLI to run scans in CI/CD.

The walkthrough shows the scan, finding review, patch generation, and pull request flow. · Best for: Developers and security teams introducing repository scans and CI/CD automation.

The presenter demonstrates a local repository scan with the Codex Security plugin, reviews a vulnerability and generated fix, then introduces the CLI for repeatable scans across repositories and CI/CD.

Check access and install the plugin0:00

  • Check for Daybreak Blue access in Settings under General.
  • Find and install the Codex Security plugin from Plugins.

Configure and run a scan1:11

  • Open the plugin and start a scan on a locally staged repository.
  • Choose a model and reasoning level; the demo uses Daybreak Blue.
  • Enable additional context to guide analysis toward a specific area, such as authentication.

Review a finding and generate a fix2:09

  • The scan prepares repository context, builds a threat model, reviews code, and produces candidate findings.
  • Review a finding’s summary, attack path, and supporting evidence.
  • Generate a patch, inspect its changes, and publish it to GitHub for the usual review process.

Use the CLI for automation4:17

  • The CLI runs the scan workflow from a locally staged repository.
  • Install it using npm, then run a scan and review or triage findings in the CLI.
  • The presenter describes the CLI as portable and suitable for CI/CD automation and multi-repository use.

Recap and suggested next step5:19

  • The workflow covers access, plugin-based scanning and fixes, and CLI-based scaling.
  • Try a scan on a familiar codebase, review findings, work through a fix, then make scanning repeatable with the CLI.

Step by step

  1. Confirm Daybreak Blue access in Codex settings.
  2. Install the Codex Security plugin.
  3. Start a scan, select a repository and model, and add focused analysis context if needed.
  4. Review findings and evidence; generate a patch and inspect the changes.
  5. Publish the proposed fix to GitHub and follow the normal pull request review process.
  6. Install the Codex Security CLI with npm, run scans, and integrate them into CI/CD automation.

Tools & resources mentioned

  • Codex Security plugin — run scans, inspect findings, and generate fixes.
  • Codex Security CLI — run and automate repository scans.
  • Daybreak Blue — model selected for the demonstrated scan.
  • GitHub — host and review the proposed fix pull request.
  • npm — install method mentioned for the CLI.
Watch on YouTube

Notes are AI-generated from the video's transcript and may miss nuance.