AI remediation

AI remediation closes the loop between finding a vulnerability and fixing it. From a finding — or a whole group of related findings — you trigger an AI fix. Vortex generates the code changes and opens a pull request in your connected repository, so the fix arrives as something your team can review and merge through its normal workflow.

Prerequisites

Before you can use Fix with AI, you need:

• A connected version-control integration (GitHub, GitLab, or Bitbucket) for the repository behind the scanned target. See Version control.
• An available remediation credit — triggering an AI fix consumes one. Credits are tied to your plan; see Billing & tiers.

Note

The pull request opens against the branch you scanned. There’s a repo default plus an optional per-scan override, so confirm you scanned the branch you want the fix to target.

How it works, end to end

1. Open a finding (or a finding group) on a Vortex report.
2. Choose Fix with AI.
3. Vortex analyzes the issue and generates the code changes.
4. It opens a pull request in your connected repository against the scanned branch.
5. The fix’s status and PR link surface on the report and in the Remediation Queue.
6. Your team reviews and merges the pull request like any other change.

How it connects to the Remediation Queue

Every AI fix becomes a card in the Remediation Queue — the Kanban pipeline that tracks fixes from finding through remediation, review, and approval. The queue is where you watch a fix’s pull request progress, approve it, and keep an audit trail of who did what. The report shows the per-finding status; the queue shows the whole pipeline across your organization.

Credits and limits

• Each AI fix you trigger consumes a remediation credit.
• Credit allowances are tied to your subscription. If you’re out of credits, the action will be unavailable — check your plan and pricing in the app.

Troubleshooting

• The Fix with AI action is unavailable. Confirm a version-control integration is connected for this target’s repository, and that you have remediation credits remaining.
• The pull request targets the wrong branch. Check the branch the scan ran against — set the repo default or use the per-scan override before scanning.
• No pull request appears on the report. Give it a moment to open, then check the Remediation Queue for the card and its status.

Next steps

• Version control — connect a repository.
• Remediation Queue — track and approve fixes.
• Findings & accepting risk