Vibe Code Web for Slack: Quickstart

Vibe Code Web for Slack lets your team start remote AI coding sessions directly from a Slack thread. The agent reads the thread context, works in an isolated cloud sandbox, and opens a GitHub pull request — without leaving Slack.

Use this guide after the Vibe Code Web Slack app has been installed and connected to your Vibe account and GitHub repositories.

1. Open Admin Settings
2. Make sure you are in the right Mistral organization. Your Mistral organization can only be connected to a single Slack Workspace.
3. In App Connections section, click Connect to Slack.
4. Complete the OAuth flow to finalise the connection. If you are not an owner of your Slack workspace, you may need to request app installation from a workspace owner.
5. Mistral Vibe is now installed in your Slack workspace. You can now connect to Slack MCP or start your first session.

Once Slack App is installed to your Slack workspace, please follow these instructions:

1. Open Vibe Work
2. Click on Slack Connector, then click Connect
3. Complete OAuth flow to connect to the right Slack workspace you have
4. Click on New Chat
5. Enjoy playing with Slack!

Vibe Code Web lets you start a remote coding session from the context already in a Slack thread. The agent uses the thread context, works in an isolated cloud sandbox, and creates a linked Vibe Code Web session. The coding agent can create a pull request for review.

Use Slack when the coding task starts from:

• an incident or on-call thread
• a CI or alert notification
• a customer or support escalation
• a product or engineering discussion
• a code review discussion summarized in Slack
• a small implementation decision already agreed in-thread

1. Find a Slack thread with enough context for the coding task. Good context includes:
   • the repository or project name
   • the bug, failing test, or desired behavior
   • links to logs, PRs, issues, or screenshots
   • constraints, such as "keep the API unchanged" or "only touch docs"
2. Mention the Vibe Code app in the thread.

   @Vibe investigate the issue described in this thread and open a PR if there is a clear fix.

   @Vibe investigate the issue described in this thread and open a PR if there is a clear fix.

3. If Vibe needs more information, answer in the thread. Common clarification questions:
   • Which repository should I use?
   • Which branch should I target?
   • Should I open a PR or only investigate?
   • Is this safe to change, or should I produce a summary first?
4. Open the Vibe Code Web session link posted by the app. Use the web session to inspect progress, command output, steer the agent, and review the resulting GitHub branch or pull request.
5. Review the final code in GitHub. GitHub remains the source of truth for code review, required checks, comments, approvals, and merge decisions.

Use prompts that are scoped, actionable, and likely to end in a branch or pull request.

For best results, include the repo, the desired outcome, and the review boundary.

@Vibe [task]

Repo/project: [repo name]
Goal: [what should change]
Constraints: [what not to change]
Validation: [test/check to run if known]
Output: open a PR / investigate only / summarize first

@Vibe [task]

Repo/project: [repo name]
Goal: [what should change]
Constraints: [what not to change]
Validation: [test/check to run if known]
Output: open a PR / investigate only / summarize first

Example:

@Vibe fix the settings persistence bug described above.

Repo/project: web-app
Goal: the alerts toggle should still be enabled after refresh.
Constraints: do not change the API shape.
Validation: run the settings tests if available.
Output: open a PR if the fix is clear; otherwise summarize what you found.

@Vibe fix the settings persistence bug described above.

Repo/project: web-app
Goal: the alerts toggle should still be enabled after refresh.
Constraints: do not change the API shape.
Validation: run the settings tests if available.
Output: open a PR if the fix is clear; otherwise summarize what you found.

After you mention Vibe Code:

1. The app reads the Slack thread context.
2. It maps the request to a Vibe Code Web project and GitHub repository.
3. If the repository is ambiguous, it asks you to choose.
4. It creates a Vibe Code Web session and posts a link back to Slack.
5. The agent works remotely in a managed sandbox.
6. The result is a GitHub branch or pull request, when a code change is appropriate.

• Start with small, scoped tasks.
• Name the repository or project when possible.
• Say whether you want a pull request or an investigation summary.
• Include the failing test, error message, stack trace, or expected behavior.
• Avoid asking for broad rewrites from Slack.
• Do not paste secrets into Slack or into the agent prompt.
• Review the resulting branch or pull request in GitHub before merging.

Good Slack-started tasks usually:

• have enough thread context
• are tied to a known repo or project
• can run in an isolated sandbox
• can be validated with tests, build output, or code inspection
• end in a GitHub branch, pull request, or investigation summary

Avoid Slack-triggered sessions for:

• broad architecture changes without a clear owner
• tasks requiring local-only services, secrets, hardware, or private networks
• vague prompts like "fix this" without logs or expected behavior
• cross-owner GitHub work unless the project and repo mapping is clear
• changes that should be manually designed before implementation

• Vibe Code Web for Slack uses AI to generate code, summaries, and pull requests. Outputs may be inaccurate — always review before merging.
• Slack thread content shared with the app is processed to fulfill your request and is not used to train Mistral models.
• For full details on data handling, retention, and your rights, see the Mistral privacy policy and trust center.