Set up Daybreak Defense Factory walks you through your first cloud scan. Local scans have separate plugin and CLI guides.
Billing
How are cloud scans billed?
Repository scans and continuous monitoring are billed by token usage at your plan’s rates, in credits or USD. Your plan’s included usage allowance does not cover these scans.
Repository scans and continuous monitoring draw from the same credit balance. In a workspace, everyone shares that balance. Free scanning credits don’t expire. When they run out, further scans are billed at your plan’s rates.
Where can I see scan costs?
Open Usage to compare costs by repository over a date range. Scan cost shows the cost before credits and exemptions. Billable remainder shows the amount remaining after credits and exemptions apply.
Scanning
Does the project need to be built for scanning?
Daybreak can analyze source without a successful build. Validation may need dependencies or a working build to reproduce an issue. Configure those requirements in the Codex cloud environment.
What languages are supported?
Daybreak analyzes source across languages. Results depend on the model’s ability to reason about the language and framework, and on the available repository context. Check the report for the scope reviewed, since coverage can vary across languages and components.
Which scan should I use?
Use a repository scan to look for issues already in the code, continuous monitoring to check new commits on the default branch, or a scheduled scan for recurring repository reviews. You can check changes before they merge with PR reviews.
Can I pause commit monitoring?
Yes. Open Repositories, select the repository, and open Continuous scanning settings. Turn off Continuous monitoring and save your changes. You can turn it back on in the same settings.
Can I edit the threat model?
Yes. Open Threat model in the monitored repository and update it when the architecture, deployment, or security assumptions change. Your edits apply to future scans. The threat model guide explains what to include.
Can I scan code hosted on GitLab?
Cloud scans use a connected GitHub repository. For GitLab, scan a local checkout or run the Codex Security CLI in GitLab CI/CD.
Findings and validation
What does validation establish?
Source analysis can establish a vulnerable code path. A successful reproducer or test can demonstrate the issue at runtime. Check the finding’s evidence and prerequisites to decide whether it applies to your system. If validation can’t run, identify what still depends on runtime or deployment behavior.
What happens if validation fails?
Inspect the attempted validation and any available logs. The issue may not apply, or the environment or test may have been unable to exercise it. Investigate before dismissing the finding.
What if the scan reports no findings?
Check that the scan completed on the intended repository and revision, and review any coverage limits or unfinished work. A report with no findings doesn’t rule out vulnerabilities.
Fixes
Does Daybreak apply patches automatically?
Daybreak saves a proposed patch for review. Fix with Codex lets you discuss or refine it. Create PR opens a draft pull request on GitHub. See Review a proposed fix.
How do I know whether a patch fixed the issue?
Check whether the original issue still reproduces and whether legitimate behavior still works. If validation is incomplete, record what remains untested. A patch, pull request, or status change alone doesn’t verify a fix.