# Vercel Agent

Vercel Security Review is in public beta for Pro and Enterprise teams: once enabled, every push to a connected GitHub repository is automatically reviewed for vulnerabilities, with findings reported in the Vulnerabilities dashboard. Reviews start from push events rather than pull requests, so direct and force pushes to the production branch are reviewed too, and every project affected by one push is reviewed together. Each finding records the project, environment, branch and commit with a summary, a suggested fix and an AI-generated severity rating; Fix with Vercel Agent has the agent propose a fix and open a pull request that nothing merges until you approve.

Vercel Security Review is in public beta for Pro and Enterprise teams: once enabled, every push to a connected GitHub repository is automatically reviewed for vulnerabilities, with findings reported in the Vulnerabilities dashboard. Reviews start from push events rather than pull requests, so direct and force pushes to the production branch are reviewed too, and every project affected by one push is reviewed together. Each finding records the project, environment, branch and commit with a summary, a suggested fix and an AI-generated severity rating; Fix with Vercel Agent has the agent propose a fix and open a pull request that nothing merges until you approve.

Vercel has added Security Review to Vercel Agent as a public beta: once a team enables it, every push to a connected GitHub repository triggers a scan. Pattern-matching scanners miss logic flaws such as missing authorization checks; this review compares each push against a base, reads the surrounding code, traces whether the change can be reached and rechecks each finding. Because it scans only the diff, a review finishes in seconds and can cover every preview and production deployment. Findings appear in pull request comments, a dashboard and the CLI, and with permission the agent can validate and push fixes.

Vercel has added Security Review to Vercel Agent as a public beta: once a team enables it, every push to a connected GitHub repository triggers a scan. Pattern-matching scanners miss logic flaws such as missing authorization checks; this review compares each push against a base, reads the surrounding code, traces whether the change can be reached and rechecks each finding. Because it scans only the diff, a review finishes in seconds and can cover every preview and production deployment. Findings appear in pull request comments, a dashboard and the CLI, and with permission the agent can validate and push fixes.

When Vercel Agent works on a production problem, it investigates automatically under read-only access, then proposes a plan listing the tasks it would do and the permissions they need, and only after the user approves that plan does it receive access beyond the read-only baseline. Access is defined by scopes, the named capabilities recognized by Vercel's authorization system; a plan requesting more than the baseline, or including supported external actions, waits for approval as a whole, and the runtime checks the plan is active before selecting its approved credential while Vercel APIs check each request against that credential's permissions.

When Vercel Agent works on a production problem, it investigates automatically under read-only access, then proposes a plan listing the tasks it would do and the permissions they need, and only after the user approves that plan does it receive access beyond the read-only baseline. Access is defined by scopes, the named capabilities recognized by Vercel's authorization system; a plan requesting more than the baseline, or including supported external actions, waits for approval as a whole, and the runtime checks the plan is active before selecting its approved credential while Vercel APIs check each request against that credential's permissions.