vercel alerts

The vercel alerts command lists recent alerts for the linked project, a specific project, or an entire team. The inspect subcommand shows details for a single alert group, and the rules subcommand tree manages alert rules from the terminal.

By default, vercel alerts reads alerts for the linked project from the last 24 hours. You can change the scope with --project or --all, filter by alert type, change the time range, and switch between table, AI investigation, or JSON output.

Use this command when you want to inspect alert activity from the terminal without opening the dashboard.

# List alerts for the linked project from the last 24 hours
vercel alerts
 
# List team-wide alerts
vercel alerts --all
 
# Filter by alert type and time range
vercel alerts --type usage_anomaly --since 2026-03-01T00:00:00.000Z

These options only apply to the vercel alerts command.

The --project option, shorthand -p, lists alerts for a specific project and overrides the linked project. Pass the project name (the name shown in the dashboard and vercel project ls) or its ID, for example my-app or prj_abc123.

vercel alerts --project my-app

You can't combine --project with --all.

The --all option, shorthand -a, lists team-wide alerts instead of using the linked project.

vercel alerts --all

You must be in team scope to use --all.

The --type option filters by alert type. You can repeat the flag or pass comma-separated values.

vercel alerts --type usage_anomaly
vercel alerts --type usage_anomaly,error_anomaly
vercel alerts --type usage_anomaly --type error_anomaly

The --ai option prints AI investigation sections instead of the default table output.

This view includes the alert title, resolved time, summary, and key findings when that data is available.

vercel alerts --ai

The --since option sets the start of the time range. Use an ISO 8601 timestamp.

If you don't pass --since or --until, the command defaults to the last 24 hours.

vercel alerts --since 2026-03-01T00:00:00.000Z

The --until option sets the end of the time range. Use an ISO 8601 timestamp.

vercel alerts --since 2026-03-01T00:00:00.000Z --until 2026-03-02T00:00:00.000Z

--since must be earlier than --until.

The --limit option sets the maximum number of alert groups to return.

The supported range is 1 through 100.

vercel alerts --limit 25

The --format option supports json output for scripting and automation.

vercel alerts --format json

When you use --format json, the command returns a groups array with the alert group payload from the API.

List alerts for the linked project:

vercel alerts

List team-wide alerts:

vercel alerts --all

Filter by usage and error anomalies:

vercel alerts --type usage_anomaly --type error_anomaly

Print AI investigation summaries for a custom time range:

vercel alerts --ai --since 2026-03-01T00:00:00.000Z --until 2026-03-02T00:00:00.000Z

Export alerts as JSON:

vercel alerts --format json

Show details for a single alert group.

vercel alerts inspect <groupId>

Inspect a group in the linked project:

vercel alerts inspect grp_abc123

Inspect as JSON:

vercel alerts inspect grp_abc123 --format json

Use rule schemas to inspect the fields available to your selected team, then create, list, inspect, update, or delete alert rules.

Use vercel alerts rules --help to see the rules command tree.

Rule IDs are returned by rules add and shown by rules ls. Use those IDs with rules inspect, rules update, and rules rm.

List alert rules that affect the linked project. Use --project to select another project or --all to list every accessible rule in the selected team.

Aliases: list.

vercel alerts rules ls

Use built-in to list built-in rules. For compatibility with previous CLI versions, rules ls --type also accepts supported built-in trigger types such as usage_anomaly and error_anomaly. Use vercel alerts rules schema --type built-in to inspect the trigger types available to your team.

# List rules for the linked project
vercel alerts rules ls
 
# List every rule in the selected team
vercel alerts rules ls --all
 
# JSON output
vercel alerts rules ls --all --format json

rules ls retrieves every available page before printing results. JSON output contains a rules array with the matching rule objects.

Fetch the API-owned authoring schema for the rule types available to the selected team. Run the command without --type to list the available types, or select a type to see its create and update fields, constraints, and examples.

vercel alerts rules schema

# Show the fields and examples for built-in rules
vercel alerts rules schema --type built-in

Create an alert rule from a JSON body file. The create body must set type. For a built-in rule, set type to built-in.

Aliases: create.

vercel alerts rules add --project my-app --body ./rule.json

Create a JSON file for the rule body, then select the rule's project scope in one of these ways:

• Add ruleScope to the body.
• Pass --project <name-or-id>.
• Pass --all for a built-in rule.

Do not combine ruleScope with --project or --all. A linked project does not supply the scope automatically when you create a rule.

Create a built-in error anomaly rule for one project:

{
  "type": "built-in",
  "name": "Production server errors",
  "triggers": {
    "mode": "selected",
    "items": [
      {
        "type": "error_anomaly",
        "filter": "statusGroup:5xx AND route:/api/*"
      }
    ]
  },
  "matchMinimumSeverityLevel": "high"
}

vercel alerts rules add --project my-app --body ./rule.json

Use vercel alerts rules schema --type built-in for additional validated examples, filter syntax, and current constraints.

The current command rejects request bodies that contain the previous alertTypes field. Rewrite saved bodies using the current schema:

Built-in filters use the syntax shown by the current schema. For example, an error anomaly filter uses statusGroup:5xx instead of the previous OData expression.

Show one alert rule by ID.

Aliases: get.

Rule IDs are unique within a team. Use the global --scope <team> option when the rule belongs to a team other than your current team. The --project and --all options are deprecated for this subcommand and do not narrow the request by project.

vercel alerts rules inspect <ruleId>

vercel alerts rules inspect ar_abc123
vercel alerts rules inspect ar_abc123 --format json

Delete an alert rule. The selected team's default rule cannot be deleted.

Aliases: remove, delete.

Rule IDs are unique within a team. Use the global --scope <team> option when the rule belongs to a team other than your current team. The --project and --all options are deprecated for this subcommand and do not narrow the request by project.

vercel alerts rules rm <ruleId>

# Delete with confirmation
vercel alerts rules rm ar_abc123
 
# Delete without prompt
vercel alerts rules rm ar_abc123 --yes
 
# Delete by using the delete alias
vercel alerts rules delete ar_abc123 --yes

Patch an alert rule from a JSON body file, change its project scope, or do both. Omitted body fields remain unchanged, and type is optional because the API infers it from the stored rule.

Aliases: patch.

vercel alerts rules update <ruleId> --body ./patch.json
vercel alerts rules update <ruleId> --project my-app

You must provide --body, --project, or --all. Do not combine a ruleScope field in the body with --project or --all.

Save the fields you want to change in a JSON file:

{
  "name": "Critical production errors",
  "matchMinimumSeverityLevel": "critical"
}

# Update fields from a file
vercel alerts rules update ar_abc123 --body ./patch.json
 
# Patch by using the patch alias
vercel alerts rules patch ar_abc123 --body ./patch.json
 
# Change scope without a body file
vercel alerts rules update ar_abc123 --project my-app

The authoring schema includes restrictions based on the stored rule. For example, the default rule accepts notification updates only.

Use --format json for scripting and automation. Rule commands write only JSON to standard output:

Validation failures return an error object with code and message. When the API identifies individual invalid fields, the object also includes an issues array with field paths and messages.

• To learn how to configure and receive alerts, see Alerts.
• If you want to automatically investigate alerts with AI, see Agent Investigation.

The following global options can be passed when using the vercel alerts command:

• --cwd
• --debug
• --global-config
• --help
• --local-config
• --no-color
• --non-interactive
• --scope
• --team
• --token
• --version

For more information on global options and their usage, refer to the options section.