What a scan examines
Each scan resolves the branch once, records the exact commit and reads only that commit together with the recorded infrastructure evidence for the environment. It looks for failure mechanisms that already exist between the code and the environment, such as a limit the current configuration can exceed or a permission a code path relies on.
What a scan reports
Supported findings with their citations, the same way a change check reports them, so a risk found between changes reads like a risk found in a pull request. Each run creates a new record and leaves earlier ones unchanged.
An absence of findings does not establish that the environment is free of risk; it establishes what the cited evidence showed at that commit.
Availability
Scheduled scanning is part of the production-agent roadmap and is not available to new workspaces today. Change checks are available now. Talk to the team about availability.
Talk to the team
Tell us which environments you would scan and how often. How the production agent works describes the shared investigation path and the evidence it cites.
Book a call