Pull anomaly alert details using the Vercel CLI
Vercel has introduced a new feature that allows users to access anomaly alerts through the Vercel CLI. The 'vercel alerts' command enables users to list alerts for specific teams or projects, providing details such as start time and alert type. Additionally, the AI investigation results can be viewed alongside each alert, streamlining the process of managing alerts directly from the terminal.
- ▪Users can access anomaly alerts directly through the Vercel CLI.
- ▪The 'vercel alerts' command lists all alerts for a team or project.
- ▪AI investigation results can be displayed alongside each alert.
Vercel Blog files mainly under programming. We currently carry 13 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Vercel Blog |
| Canonical URL | https://vercel.com/changelog/pull-anomaly-alert-details-using-the-vercel-cli |
| Publication time | 2026-05-21T09:00:00.000Z |
| Retrieval time | 2026-05-21T08:51:10.385Z |
| Last seen | 2026-05-21T08:51:10.385Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | binEmDhSo3s3 |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
1 min readCopy URLMay 21, 2026You can now access anomaly alerts and their details directly through the Vercel CLI.With the vercel alerts command, you can list all alerts for a team or given project. For each alert, you can view the start time, the type of alert, and whether or not the alert is still active.With the --ai option, the AI investigation results appear alongside each alert. You and your agent can act on alerts without leaving the terminal.vercel alerts --aiShows alert details with AI investigation results inline.Available on Observability Plus.Learn more about vercel alerts in the CLI documentation.
Excerpt limited to ~120 words for fair-use compliance. The full article is at Vercel Blog.
Discussion
0 commentsMore from Vercel Blog
