--- title: Amp Is Now In Slack link: https://ampcode.com/news/slack-integration source: ampcode-com published: 2026-07-20T00:00:00Z updated: 2026-07-20T00:00:00Z first_seen: 2026-10-03T23:09:50.514863041Z summary: 'You can now summon Amp in Slack. Connect your workspace from Amp''s settings, then mention @Amp in any channel or thread. Amp sends your message to your personal Puck, which can initiate bug fixes, spike new features, answer questions about your codebase, and find and manipulate existing threads. Here are a few examples of how we''ve been using it: ← 1 / 4 → Fix a User Bug Report A user reported a bug with a screenshot. Amp read the screenshot, reproduced the issue, and posted back a fix. Resolve a Production Incident A production alert posted to a Slack channel, Amp identified the likely culprit commit, pulled production logs to verify, and pushed a fix to the production Terraform config. See full investigation thread. Close the Loop with Your Team Two teammates investigated the same issue. One resolved it and asked Amp to ping the other user from their investigation thread. The other user then archived their ongoing threads from Slack. Search Slack for Context Amp can also search through Slack to pull discussions relevant to its current task. The Amp Slack integration compiled the examples used in this post. Install the Slack Integration Open Workspace Integrations as an Amp workspace admin, select Connect a Slack Workspace, and authorize the Amp app in Slack. (If you don''t yet have an Amp workspace, create one.) Individual users should link their Amp user directly with their Slack user in Personal Settings. Mention @Amp in any Slack channel or thread. Read the Amp manual for more details.' content: extracted html: 2026-07-20-amp-is-now-in-slack.html preview: file: 2026-07-20-amp-is-now-in-slack.preview-1ee4d0780647.webp width: 256 height: 134 color: '#5d564c' images: - source: https://ampcode.com/og?_template=news&_version=7&title=Amp+Is+Now+In+Slack&date=July+20%2C+2026&tagline=Summon+Amp+from+Slack&sig=b2399e0d18d6884cd50c8c3bcf6493bffbe8addfab9d2344a175f2f4802f1362 original: file: 2026-07-20-amp-is-now-in-slack.image-85121c618d19.png width: 1200 height: 630 variants: - file: 2026-07-20-amp-is-now-in-slack.image-26d3b03e1d65.webp width: 320 height: 168 - file: 2026-07-20-amp-is-now-in-slack.image-f4edb98ab6e2.webp width: 640 height: 336 - file: 2026-07-20-amp-is-now-in-slack.image-551e5cb3ee86.webp width: 960 height: 504 - file: 2026-07-20-amp-is-now-in-slack.image-c654d2f6a3e2.webp width: 1200 height: 630 color: '#221b16' - source: https://static.ampcode.com/news/slack/user-bug.png original: file: 2026-07-20-amp-is-now-in-slack.image-60e7c13e930e.png width: 1662 height: 1242 color: '#fdfdfd' - source: https://static.ampcode.com/news/slack/resolve-incident-magical.png original: file: 2026-07-20-amp-is-now-in-slack.image-9c9a324dc54e.png width: 1192 height: 582 color: '#fdfdfd' - source: https://static.ampcode.com/news/slack/notifying-a-teammate.png original: file: 2026-07-20-amp-is-now-in-slack.image-cfee65d6564d.png width: 1344 height: 1532 color: '#fdfdfd' - source: https://static.ampcode.com/news/slack/search-slack.png original: file: 2026-07-20-amp-is-now-in-slack.image-e1a9938eeaaa.png width: 1432 height: 1154 color: '#f9fcf6' --- You can now summon Amp in Slack. Connect your workspace from [Amp's settings](https://ampcode.com/workspace/integrations), then mention `@Amp` in any channel or thread. Amp sends your message to your personal [Puck](https://ampcode.com/news/meet-puck), which can initiate bug fixes, spike new features, answer questions about your codebase, and find and manipulate existing threads. Here are a few examples of how we've been using it: 1 / 4 ## Fix a User Bug Report A user reported a bug with a screenshot. Amp read the screenshot, reproduced the issue, and posted back a fix. ![Using Amp in Slack to investigate and fix a user bug report](https://static.ampcode.com/news/slack/user-bug.png) ## Resolve a Production Incident A production alert posted to a Slack channel, Amp identified the likely culprit commit, pulled production logs to verify, and pushed a fix to the production Terraform config. ![Using Amp in Slack to root-cause and resolve a production incident](https://static.ampcode.com/news/slack/resolve-incident-magical.png)\ [See full investigation thread.](https://static.ampcode.com/news/slack/resolve-incident-detail.png) ## Close the Loop with Your Team Two teammates investigated the same issue. One resolved it and asked Amp to ping the other user from their investigation thread. The other user then archived their ongoing threads from Slack. ![Puck notifying a teammate in Slack that an issue has been resolved](https://static.ampcode.com/news/slack/notifying-a-teammate.png) ## Search Slack for Context Amp can also search through Slack to pull discussions relevant to its current task. The Amp Slack integration compiled the examples used in this post. ![Using Amp to search Slack messages for context](https://static.ampcode.com/news/slack/search-slack.png) ## Install the Slack Integration 1. [Open Workspace Integrations](https://ampcode.com/workspace/integrations) as an Amp workspace admin, select **Connect a Slack Workspace**, and authorize the Amp app in Slack. (If you don't yet have an Amp workspace, [create one](https://ampcode.com/workspace).) 2. Individual users should link their Amp user directly with their Slack user in [Personal Settings](https://ampcode.com/settings/integrations). 3. Mention `@Amp` in any Slack channel or thread. [Read the Amp manual for more details.](https://ampcode.com/manual#slack)