megachangelog
Announcement

Vercel Agent now available in Slack code channels

Vercel Agent is now integrated with Slack code channels, allowing teams to collaborate with an AI coding agent directly in dedicated channels. The agent can follow work, accept instructions, review code and pull requests, and execute changes with approval workflows, all while maintaining audit trails and respecting user permissions.

Vercel Agent now works in Slack code channels, a new kind of channel launched today for working with a coding agent. Anyone in the channel can follow the work, give Agent new instructions, and review the code it writes.

Choose from the Slack sidebar, select Vercel as the agent, and describe what you need to get started. You can also ask Agent to create one from an existing channel or thread. It brings that context with it to the new channel.Create a code channel

Use code channels to investigate incidents, write and review code as a team, or manage ongoing work such as dependency upgrades and migrations.

Inside a Vercel Agent code channel:

Vercel Agent in Slack code channels is available in public beta for Pro and Enterprise teams. Add , learn about , or read the .Vercel to SlackSlack Codedocs

Read more

  • Agent posts relevant deployments, logs, errors, and diffs in the channel as it works.Follow the work:

  • Agent follows the conversation, recognizes which messages are for it, and continues when the team gives it more work.Talk without repeated mentions:@Vercel

  • Ask Agent for a PR review and it posts its findings in the channel. It can find bugs outside the diff, and explain failing checks and their root causes.Review pull requests:

  • Agent is read-only by default and never exceeds the requester's permissions. Before making a change, it drafts a plan and waits for approval. For every action, Vercel records who requested and approved it and what Agent ran.Approve every change:

  • The person who created the code channel can cancel an active task.Stop work at any time:

slackagentcollaborationaibeta

Source: original entry ↗