---
type: "post"
slug: "vercel-agent-comes-to-slack"
title: "Vercel Agent comes to Slack"
description: "Vercel Agent now answers in Slack threads with deployment, log and metric context already loaded, turning an incident conversation directly into changes a human approves."
retrieval_nugget: "Vercel Agent now answers in Slack threads with deployment, log and metric context already loaded, turning an incident conversation directly into changes a human approves."
published_at: "2026-08-30"
updated_at: "2026-09-12"
record_date: "2026-08-25"
date_kind: "discovered_at"
topics: ["agent-integrations","agents","ai","mcp"]
entities: ["Vercel"]
source_url: "https://vercel.com/blog/introducing-vercel-for-slack"
source_title: "Introducing Vercel for Slack"
source_domain: "vercel.com"
source_terms: ["Vercel","Slack","your","changes","Work"]
summary_word_count: 186
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:vercel-agent-comes-to-slack"
status: "published"
source_urls: ["https://vercel.com/blog/introducing-vercel-for-slack"]
visuals: []
editorial_provenance: {"schema_version":"newruntime-editorial-copy-v1","content_status":"source_grounded_final","final_copy_sha256":"sha256:3ef8d70cb7234e5373e03c6058967b9ee9d9cc2aa038b7173e5f7aef1f684d0f","reviewed_at":"2026-09-12T10:00:00Z","source_evidence_count":1,"verified_claim_count":2,"site_analysis_schema_version":"newruntime-site-analysis-v1","site_object_kind":"field_note","observed_fact_count":2,"implication_count":1,"watch_condition_count":1,"related_record_count":2}
analysis: {"schema_version":"newruntime-site-analysis-v1","object_kind":"field_note","thesis":"Vercel put its agent into Slack in public beta for Pro and Enterprise teams.","observed_facts":[{"text":"Vercel for Slack is available in public beta for Pro and Enterprise teams and responds to an @Vercel mention in channels, threads and direct messages.","source_urls":["https://vercel.com/blog/introducing-vercel-for-slack"]},{"text":"The agent investigates logs, metrics and deployments to propose a root cause and a fix, and flags risky changes on a pull request.","source_urls":["https://vercel.com/blog/introducing-vercel-for-slack"]}],"mechanism":"Because the agent is part of the platform, deployments, build statuses, logs, metrics, code reviews and pull requests are in front of it before anyone types, so the expensive part of an incident conversation — assembling the evidence — is skipped rather than delegated.","why_now":"Vercel describes the agent as the first responder for production apps: when something changes it investigates logs, metrics and deployments, proposes a root cause and a fix, and on a pull request flags regressions a passing CI run would not show.","implications":["the chat surface is where intent is expressed, but the authority and the evidence live in the platform behind it"],"evidence_boundary":"This is a public beta announcement, and the approval step is described rather than specified.","watch_conditions":["The condition to watch is whether a Slack-initiated change carries the same review record as one opened from a terminal, because an agreement in a thread is not an audit trail."],"related_records":[{"url":"https://newruntime.com/posts/organization-agent-runtime-qm-vercel-eve","relation":"Prior coverage of the scoped runtime behind an organization agent."},{"url":"https://newruntime.com/topics/agents","relation":"Topic hub for agent surfaces and their authority boundaries."}]}
routes: {"html":"https://newruntime.com/posts/vercel-agent-comes-to-slack/","markdown":"https://newruntime.com/posts/vercel-agent-comes-to-slack.md","json":"https://newruntime.com/posts/vercel-agent-comes-to-slack.json"}
---

# Vercel Agent comes to Slack

## Retrieval answer

Vercel Agent now answers in Slack threads with deployment, log and metric context already loaded, turning an incident conversation directly into changes a human approves.

Vercel put its agent into Slack in public beta for Pro and Enterprise teams. Mentioning @Vercel in a channel, thread or direct message starts a session that reads the discussion and answers with the state of the platform running the app, then turns what the team agreed into changes someone approves. Vercel describes the agent as the first responder for production apps: when something changes it investigates logs, metrics and deployments, proposes a root cause and a fix, and on a pull request flags regressions a passing CI run would not show.

The mechanism is context that is already present rather than context the user supplies. Because the agent is part of the platform, deployments, build statuses, logs, metrics, code reviews and pull requests are in front of it before anyone types, so the expensive part of an incident conversation — assembling the evidence — is skipped rather than delegated.

That is the distinction drawn in [an organization agent being a scoped runtime rather than one Slack bot](https://newruntime.com/posts/organization-agent-runtime-qm-vercel-eve/): the chat surface is where intent is expressed, but the authority and the evidence live in the platform behind it. The [agents hub](https://newruntime.com/topics/agents/) tracks that split as more vendors put a mention handle in front of production systems.

This is a public beta announcement, and the approval step is described rather than specified. The condition to watch is whether a Slack-initiated change carries the same review record as one opened from a terminal, because an agreement in a thread is not an audit trail.