GitHub has announced the general availability of AI Scan for pull requests and Agentic Autofix for code scanning alerts.[1][2] These features bring AI assistance closer to the work of securing code. They do, however, operate on different scopes: proposed changes for the former, alerts on the default branch for the latter. For businesses, the challenge is to prepare fixes more effectively while keeping technical validation in place before they are merged.
AI Scan reviews changes before they are merged
A pull request is used to propose a change and have it reviewed before it is merged. AI Scan complements CodeQL there, notably for PHP, Bash, Terraform and certain less well-covered frameworks. Once enabled alongside code scanning, it surfaces findings flagged as AI-generated, sometimes accompanied by an explanation and a suggested fix.[1]
These findings remain advisory: they do not cause the code scanning check to fail and do not block merging via ruleset requirements. AI Scan does not process pull requests from forks or those created by Dependabot.[1] A team must therefore organise how these findings are read and dealt with, without assuming that their presence automatically holds up a release.
Agentic Autofix prepares a fix from an existing alert
Agentic Autofix can be assigned a code scanning alert located on the default branch. It explores the relevant files, proposes a change, re-runs CodeQL and can iterate before opening a draft pull request for review.[2]
GitHub explicitly excludes alerts that exist only in a pull request or another branch from this assignment to Copilot.[2] The two new features should therefore not be described as an automatic pipeline in which every AI Scan finding is immediately handed over to Agentic Autofix.
An alert disappearing on a new scan gives a useful indication about the targeted issue. It does not prove that the application retains all its expected behaviour, nor that the change introduces no other defect. Functional tests and a review of the change remain necessary.
Two paths and a human decision
The table distinguishes between the announced features and the responsibility of the team using them.
| Stage | What GitHub provides | Team check |
|---|---|---|
| Detection during review | AI Scan flags risks in proposed changes.[1] | Assess the risk and decide how to handle it before merging. |
| Preparing the fix | Agentic Autofix works on an alert from the default branch.[2] | Review the modified files and the relevance of the fix. |
| Validation | A new CodeQL scan accompanies the agent’s work.[2] | Also check business tests and side effects. |
Access conditions matter when choosing a pilot
AI Scan is available for public repositories; private or internal organisation repositories require GitHub Code Security or GitHub Advanced Security. A Copilot licence is not required.[1] Agentic Autofix is aimed at customers of these offerings on GitHub Enterprise Cloud, with administrative activation and a defined Copilot billing method.[2]
Both features consume Code Security AI credits; Agentic Autofix also uses GitHub Actions minutes.[1][2] Before rolling out, SMEs need to check their plan, the scope of repositories and the associated budget. The economic benefit will depend as much on review time as on the number of fixes actually accepted.
SMEs can evaluate results in two distinct situations
First illustrative scenario: a team modifies a PHP form and receives a finding in its pull request. The developer checks whether user input can actually reach the sensitive operation, examines the suggestion, then adds a test reproducing the case. A plausible answer from the AI is not enough to establish whether the risk exists or has gone away.
Second scenario: a code scanning alert already exists on the default branch of an eligible repository. The team assigns it to Agentic Autofix, then reviews the proposal. It checks that the fix does not inadvertently change access rights, accepted formats or business results. These scenarios are an evaluation approach, not published customer results.
The pilot can track the time to a validated fix, the proportion of suggestions retained and the regressions detected. Counting only closed alerts could mask an excessive verification workload or unsuitable changes.
Developers must understand the vulnerability as well as the fix
This development raises the bar for Web Programming and Management. Reading code remains essential to understand the path data takes, spot a fragile assumption and determine whether the fix addresses the root cause. Professionals must be able to explain why a change reduces the risk.
The skill is also reflected in the quality of tests. A case that fails before the fix and passes afterwards provides a useful benchmark, to be complemented by checks on legitimate uses. In particular, a stricter control must not prevent a necessary function from working or shift the vulnerability elsewhere.
Finally, the developer organises the review and documents decisions. They must know when to accept a suggestion, modify it or reject it. Delegating to an agent can speed up preparatory work, but command of the application remains essential to decide what gets merged.
Editor’s note
The progress to measure is a fix that is understood, tested and maintainable. These tools can help reduce research and preparation work; their real value will depend on the coverage of the scans and on teams’ ability to verify the proposals.
Further reading
Four CCCLX reads on assisted development and software security.
Sandbox, terminal, policies: GitHub puts guardrails on its code agents
Project Glasswing: Anthropic goes on the offensive against software vulnerabilities
Open-source security changes scale: IBM, Red Hat and Palo Alto join forces
With Code Layers, Figma brings design and development firmly together
Sources
- 01
GitHub Changelog (15 October 2026). “AI Scan for pull requests generally available”. Overview of the general availability, scope and terms of use of AI Scan.
- 02
GitHub Changelog (15 October 2026). “Agentic autofix for code scanning alerts general availability”. Details of how Agentic Autofix works, its access conditions and billing.
AI propels Nokia: data centres are reshaping the networking market
The AI explosion is transforming the infrastructure market Nokia is reaping the full benefits of the rise of artificial intelligence and the proliferation of data centres that comes with it. In the second quarter of 2026, the company’s Network Infrastructure business...
Gemini 3.5 Pro delayed: Google under pressure in the AI race
The race for AI models is speeding up Google is going through a difficult period in the competition over advanced artificial intelligence models. According to several reports in the specialist press, the launch of Gemini 3.5 Pro has reportedly been pushed back by...
Project Glasswing: Anthropic goes on the offensive against software vulnerabilities
A new step for AI applied to cybersecurity Anthropic is pressing ahead with Project Glasswing, an initiative that makes its Claude Mythos Preview model available to specialist cybersecurity players in order to identify and fix vulnerabilities in critical software. The...
Cloud, AI, defence: AWS steps up on every front
AWS makes artificial intelligence a pillar of critical infrastructure At the AWS Summit Washington, D.C. 2026, Amazon Web Services unveiled several developments aimed at government departments, public bodies and critical sectors. The company is strengthening its...
MDASH: the AI helping Microsoft secure Windows
Microsoft hands part of the bug hunt to artificial intelligence Cyberattacks are evolving ever faster, forcing software vendors to detect vulnerabilities before they can even be exploited. To meet this challenge, Microsoft has unveiled MDASH (Microsoft Detection and...
Microsoft speeds up its cybersecurity with AI: defence moves to machine scale
Microsoft wants to regain the upper hand against cyberattacks Cybercriminals are now using artificial intelligence to discover vulnerabilities, automate their attacks and speed up their malicious campaigns. In response, Microsoft is pressing ahead with its Secure...
Free access to Claude Fable 5 extended as Anthropic holds off
A new generation of AI designed for specific uses OpenAI is changing its strategy with the launch of GPT-5.6, a new family of models made up of Sol, Terra and Luna. Rather than offering a single model capable of meeting every need, the company is now betting on a...
OpenAI bets on modular AI with Sol, Terra and Luna
A new generation of AI designed for specific uses OpenAI is changing its strategy with the launch of GPT-5.6, a new family of models made up of Sol, Terra and Luna. Rather than offering a single model capable of meeting every need, the company is now betting on a...
Anthropic’s AI is advancing at a pace that worries cybersecurity specialists
AI models cross a new capability threshold Barely a month after its launch, Claude Mythos Preview is already improving its performance. According to the latest tests published by the UK’s AI Security Institute (AISI), Anthropic’s model now beats its own results from...
Lumo AI 2.0 speeds up without sacrificing data protection
Proton wants to prove that a high-performing AI can also be private The artificial intelligence race is no longer played out solely on model performance. User trust and data protection are now becoming major differentiators. With Lumo AI 2.0, Proton is upgrading its...
