Slack Integration
Amp is an AI agent that can build software and automate common knowledge work. Mention @Amp in a
channel or thread to ask a question, start work, or manage an existing Amp thread without leaving
Slack.
Install Amp for Slack
Use these steps if you are not signed in to Amp:
- Select Add to Slack above.
- Sign in to your Amp account. If you do not have an account, select Sign Up and create one.
- Find Slack in Personal Integrations and select Connect Slack.
- Review the requested permissions in Slack, choose the Slack workspace, and authorize Amp.
If you belong to an Amp workspace, you can connect your own Slack in Personal Integrations at any
time. This lets you mention @Amp in Slack and gives your Amp threads Slack tools that read,
search, and post as you. You do not need an admin to connect your Amp workspace first, although
your Slack workspace may require approval to install apps. An Amp workspace admin can connect
Slack in Workspace Integrations for the workspace. Your Amp workspace’s Slack restrictions still apply.
After Slack authorizes Amp, Amp shows a Slack Connected confirmation with the next steps. Add @Amp to a Slack channel, then mention @Amp in a channel or thread to start work.
What You Can Do
Puck can use messages, threads, and attached images as context. Here are some ways people use it:
Conversations and Replies
The first mention starts a Puck conversation for that Slack thread. Puck replies in the same thread so the discussion and results stay together.
When a request starts longer work, Puck replies with a link to the thread doing it, then stays quiet until the work finishes, is blocked, or needs you, when it posts one new reply. While the work runs, Slack’s working indicator briefly shows each new step, and shows that the work is waiting for input in Amp for as long as it waits. To make Puck stop posting in a thread, ask it to; it reacts to confirm instead of replying.
Mention @Amp again when you want to give Puck another instruction. Open the linked Amp thread when you want to inspect the complete conversation or continue in the app.
Amp only sees conversations it belongs to. If you mention @Amp in a direct message or group DM
between people, Slack does not tell Amp, so nothing happens and Amp cannot reply. Message Amp
directly or mention it in a channel it has been added to instead.
Each person talks to their own Puck. The working status and reply byline identify whose Puck is answering. A personal Puck uses that person’s permissions and personal connections, so two people can get different results in the same Slack thread. Workspace admins can instead have new requests in public channels run as a service account; see Integrations › Slack.
Existing conversations keep their Puck. For new conversations, Amp uses the workspace’s configured service-account Puck in public channels when the sender is eligible. Otherwise it uses the sender’s Puck. Without an Amp workspace Slack connection, the sender must have a personal Slack connection. Those conversations start as private Amp threads, even in public Slack channels, and are not automatically routed to workspace Spaces. To send the work to a Space, name it or paste its link in the conversation. Linking Slack channels to a Space needs the Amp workspace Slack connection.
Use workspace projects for code and guidance that every member must access. Add shared tools as workspace MCP servers. Keep private accounts and credentials in personal integrations and MCP settings.
Posting to Slack
Amp can send, edit, and delete Slack messages and add reactions for you, as you or as @Amp. By
default, it asks first: Amp shows you each change and makes it only after you approve it, and
you can edit a message before it is sent.
To let Amp make these changes without asking, set Posting to Slack to Allow on the Slack card in Settings → Integrations & MCP.
When an answer is structured, Amp can post a native Slack card with fields, tables, charts, and reply buttons. The approval dialog lists everything a card shows, and clicking a reply button answers Amp as you.
Slack card reference for agents
slack_write takes card: { title?, subtitle?, blocks }. Slack shows the card instead of the
message text, which becomes only the notification. The title holds up to 150 characters, the
subtitle up to 2,000, and a card has 1 to 45 blocks, each { type, ... }:
| Block | Fields | Limits |
|---|---|---|
text | text (Slack mrkdwn), muted for small gray text | 3,000 characters |
fields | fields: [{ label, value }], shown in two columns | 10 fields; label 200, value 1,700 characters |
table | headers, rows, optional caption; sortable in Slack | 1 per card; 20 columns, 100 rows, one cell per header, 10,000 characters in all |
chart | chart (bar, line, or area), title, categories, series: [{ name, values }] | Title 50 characters; 20 unique categories; 12 series with unique names and one value per category; labels 20 characters |
pie | title, segments: [{ label, value }] | 12 positive segments; labels 20 characters |
image | url (https), alt | Slack must be able to fetch the URL |
links | links: [{ label, url }], shown as buttons that open the URL | 25 links; labels 75 characters |
buttons | buttons: [{ label, style }], with style primary or danger | 5 buttons; labels 75 characters |
divider | none |
A card holds at most 1 table and 2 charts, counting pies. Empty table cells show as ”—“. A reply button click reaches the agent as that person’s reply with the button’s label.
Slack MCP Support
Puck accesses Slack through Amp’s built-in Slack tools, such as slack_read and slack_write.
These are not Slack MCP calls. Connect Slack in Personal Integrations using the steps above to
use the native integration; you do not need to configure Slack’s hosted MCP server for Puck.
Slack’s hosted MCP server is a separate integration configured in MCP settings. Support for Slack’s hosted MCP server is coming soon, pending Slack approval. Once available, it will let agents in Amp search Slack and take actions you request, limited to content your Slack account can access.
Notices
A paid Slack plan is required to use Amp in Slack’s AI agent app container. On Slack Free, users
can still mention @Amp in channels and threads, receive threaded replies, and get supported Amp
link previews.
Amp uses large language models and can generate inaccurate responses, summaries, code, findings, or other outputs. Review its work and test code before relying on it or taking production action.
Amp does not train on your data. Read the Privacy Policy for more information.