Skip to main content
Your team spots a confusing error message in Slack. Mention Replit, share the repository, and describe the improvement. Continue in the same thread to check the change and ask Agent to open a pull request, or PR: a proposed change your team can review before merging.

​
Best for

  • Support teams improving an error message after a customer conversation.
  • Product managers requesting a small, clearly defined behavior change.
  • Teammates proposing copy fixes without editing code themselves.

​
Tools

​
Add Replit to your Slack workspace

1

Open your team workspace settings

In Replit, switch to your team workspace and open Settings → Workspace overview. Under External platforms, select Manage next to Slack. Workspace editors and higher roles can add the bot; admins manage an existing bot.
2

Install the Slack bot

Choose a Slack handle, such as @Replit, then select Add to Slack. Authorize the app in the Slack workspace your team uses and return to Replit. Wait for the status to show Installed.If Slack requires admin approval, ask your Slack administrator to approve the app, then select Finish install in Replit.
3

Link your own Replit account

Invite the bot to a Slack channel and mention it, or open a DM with it. Follow the private account-link prompt, check the Replit account and team workspace shown, and select Allow. Each teammate links their own account.
4

Start your request

In a channel, mention @Replit with your repository link and the change you want. Continue in the same thread and mention the bot on each follow-up. Replit uses your linked account’s permissions.
If Slack is missing from External platforms, ask a workspace admin to check availability. See Replit on Slack for the full setup guide and troubleshooting.
The Replit Slack bot and the Slack connector are separate. The bot lets you talk to Agent in Slack. The connector is needed separately if you want Agent to search other Slack messages as a tool.
Choose one small change with a clear expected result. Include the necessary context in your request rather than assuming Agent can read every channel. Use a channel whose members are allowed to see the code details and results. Before sending your request, make sure GitHub is connected in your Replit team workspace and the target repository is available in Repositories. Your connected GitHub account needs write access to that repository.

​
Prompt the agent

Post the prompt below in a Slack channel where you have invited Replit. You can also send it directly to the bot in a DM, without the mention.

​
What to expect

1

Agent investigates the request

Agent locates the relevant code and checks the repository instructions. If the expected behavior is unclear, it asks for clarification.
2

Agent makes and checks the change

Agent updates the relevant files, keeps the change focused, and runs the relevant checks. It reports any failures or checks it could not run.
3

Get the pull request in Slack

Agent commits the change to a branch, pushes it, and opens a PR for review. It shares the PR link in the same Slack thread, with a summary of what changed and the check results.
You get a GitHub PR your team can review using its usual process. Opening a PR does not mean the change is merged or live. If setup or an approval requires the browser, select View in Replit to continue the same chat.

​
Make it work for you

​
Troubleshooting

Invite the bot and mention it on each request, including follow-ups.
The Slack session belongs to the person who started it. That person must complete approvals.
Check repository write access and ask Agent to explain the specific GitHub error.
Select View in Replit and continue the same chat there.

Replit on Slack

Set up the bot, link your account, and understand thread permissions.

Contribute to a GitHub project

Start a focused repository change directly from a Replit chat.