Slack

The v0 Slack bot lets anyone on your team contribute to production by mentioning @v0 in a Slack channel. v0 reads the conversation thread for context, writes the code changes, creates a branch, and opens a pull request -- all without leaving Slack.

With the Slack bot, your team can:

• Ask v0 to make changes to any connected GitHub repository
• Attach images and files so v0 has additional visual or document context
• Iterate in threads -- tag @v0 again in a thread to continue the conversation on the same branch
• Set a default repo per channel so nobody has to specify a repo every time

How it works

When you mention @v0 in Slack:

1. v0 reacts with a 👀 emoji to acknowledge your message.
2. v0 posts a reply with a link to the v0 chat (for example, "On it.").
3. v0 reads the thread for context, makes the code changes, and creates a branch.
4. v0 opens a pull request with a summary and a link back to the Slack thread.
5. Vercel generates a preview deployment on every commit pushed to the branch, so your team can view and QA changes directly in the browser.

Setup

Install the Slack app

Visit v0.app/slack/install to add v0 to your Slack workspace. Depending on your workspace settings, you may need Slack admin permissions or workspace-level app approval to complete the installation.

Link your Vercel account

The first time you mention @v0 in Slack, it will prompt you to link your Vercel account. During this step you select which Vercel team to connect. This determines which repositories and projects v0 can access.

Usage

Mention @v0 followed by your request in any channel where the bot is installed:

@v0 Add a dark mode toggle to the settings page

Specifying a repository

Use a structured syntax to tell v0 exactly which repository to target:

@v0 [repo=acme/dashboard] Add a chart to the analytics page

To target a specific branch:

@v0 [repo=acme/dashboard branch=feature-x] Fix the broken tooltip

Vercel project names, deployment URLs, and project IDs work as well:

@v0 Fix the header on https://my-app-abc123.vercel.app

If you don't specify a repo, v0 will try to intelligently infer the repository from your message, so you can also write naturally:

@v0 Update the login page in the acme/website repo

Continuing in threads

To continue a conversation, reply in the thread and tag @v0 again. v0 remembers the full thread and works within the same v0 chat and branch, so you can iterate on changes without starting over.

Messages in the thread that don't tag @v0 are regular Slack messages -- you can discuss changes with your team in the same thread without triggering another generation.

If you tag @v0 with a different repo in an existing thread, v0 starts a new chat for that repo.

Channel settings

Use @v0 settings in any channel to open the channel settings modal. From here you can configure:

• Default Repository -- An org/repo value that applies to every request in the channel. Once set, team members can mention @v0 without specifying a repo each time.
• Default Branch -- The branch v0 should target by default for the channel.

Settings apply to the channel, not per user. The first time someone uses a repo in a channel that does not have a default configured, v0 will suggest setting one.

Commands

Previewing changes

You can use the Slack bot even if a full preview of your repository does not load inside v0. Once v0 opens a pull request, Vercel generates a preview deployment on every commit pushed to that branch. You can use these preview deployment URLs to view and QA your changes directly in the browser, without needing the v0 in-app preview at all.

This makes the Slack bot a great fit for repositories of any size or complexity -- your team can request changes in Slack and review the results through Vercel preview deployments.