跳到正文
Amp Chronicle·· 2026-07-20AI 評分57

Amp 推出 Slack 整合功能

Amp Is Now In Slack

AI 導讀

Amp 現已支援 Slack 整合,管理員連結工作區後,用戶可在任何頻道或討論串提及 @Amp,將訊息交給個人 Puck 處理。Puck 可修復錯誤、探索新功能、回答程式碼庫問題,並搜尋及管理現有討論串。文中案例包括讀取截圖、重現並修復用戶回報的錯誤,以及透過生產環境日誌核實可能相關的提交,並修正生產環境 Terraform 設定。

正文

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.

Using Amp in Slack to investigate and fix a user bug report

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
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.

Puck notifying a teammate in Slack that an issue has been resolved

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

Install the Slack Integration

  1. 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.)
  2. Individual users should link their Amp user directly with their Slack user in Personal Settings.
  3. Mention @Amp in any Slack channel or thread.

Read the Amp manual for more details.

來源:Amp Chronicle · ampcode.com