Amp Agent

Description Features Permissions Security & Compliance

Amp is an agent that helps your team build software, fix bugs, and automate engineering tasks.How Amp works in SlackAn Amp workspace admin connects the Slack workspace. Each member then connects their Amp account to their Slack user. Mention @Amp in a channel or Slack thread where Amp is available. Amp reads relevant messages in that thread and can use attached images as context. It sends the request to the member's personal Amp assistant, Puck, and replies in the same Slack thread. Mention @Amp again to add an instruction or continue the work.On a paid Slack plan, members can also open Amp in Slack's AI agent app container and chat with it there.When a connected member shares a supported Amp link, Amp can add a preview if that member has access to the linked content.What you can ask Amp to do• Investigate a bug report, inspect code or screenshots, and suggest or make changes.
• Investigate an incident with available logs and connected tools, then report findings and possible changes.
• Explore a codebase and build or revise a feature.
• Turn feedback or an engineering request posted in Slack into a new Amp thread.
• Find, check, or manage existing Amp work.
• Search available Slack messages for context when asked.Slack plan requirementsA paid Slack plan is required to access Amp in Slack's AI agent app container. On Slack Free, users can still mention @Amp in channels and threads, receive Amp replies in those threads, and get supported Amp link previews.Amp account and usage requirementsAn Amp account with available usage is required. Amp agent and tool use consumes Amp usage.Large language model warningAmp uses large language models. It can generate inaccurate responses, summaries, code, findings, or other outputs. It can also misunderstand a request. Review its outputs, code changes, and test results before relying on them, merging changes, or taking production action.

Amp Agent will be able to view:

Amp Agent will be able to do:

Review the details to better understand this app’s security practices. To learn more about assessing apps for your workspace visit our Help Center.

General

Privacy & data governance

Data retention policy

Amp stores Slack OAuth bot tokens and Slack workspace, app, bot, and user identity metadata. Slack messages can create Amp threads that store message text, Slack identifiers, source-message snippets, channel and thread metadata, custom emoji URLs, and supported image attachments. Amp retains personal information while an account is active or as needed to provide the service, perform contractual obligations, meet tax, legal, and audit obligations, resolve disputes, preserve legal rights, or enforce agreements. Explicitly deleted thread data is removed within 30 days. Personal threads and non-Enterprise workspace threads are deleted when the user deletes the account. Enterprise workspace threads and author attribution remain when the user leaves or deletes the account and are removed when the Enterprise contract ends. See https://ampcode.com/privacy-policy for more information.

Data archiving and removal policy

Archiving an Amp thread removes it from the active thread list, but the thread remains stored, viewable, and available by URL. Deleting a thread starts removal of its thread data, which is completed within 30 days. When Slack reports an app uninstall or bot-token revocation, Amp deletes the stored Slack app installation and bot token. A personal disconnect deletes the personal Slack connection. A workspace disconnect deletes the Amp workspace binding. These actions do not delete existing Amp threads, Slack origin metadata, attachments, or Slack automation event records. Deleting an Amp account deletes personal threads and non-Enterprise workspace threads. Enterprise workspace threads and author attribution remain until the Enterprise contract ends. See https://ampcode.com/privacy-policy#how-do-i-update-or-delete-my-personal-information-from-amp for more information.

Data storage policy

Amp stores Slack integration data in its multi-tenant Amp Server environment in a multi-tenant Google Cloud Platform project. Primary infrastructure and stored user and thread data are in the United States. Stored Slack data can include the OAuth bot token, Slack workspace and user identity metadata, message content, message snippets, Slack identifiers, thread metadata, supported image attachments, and automation event records. All traffic in transit is encrypted with TLS 1.2 or later. Amp Server data, including database volumes and backups, is encrypted at the volume level with AES-256. Slack data needed for an AI response is sent to the applicable model provider. Amp-managed inference currently uses provider infrastructure in the United States. A customer-managed model connection uses the customer’s provider account and is subject to that provider’s storage terms and selected region. See https://ampcode.com/privacy-policy#data-storage-security-deletion-and-retention for more information.

App/service has sub-processors

yes

Guidelines for sub-processors

https://ampcode.com/security#infrastructure-and-service-providers

App/service uses large language models (LLM)

yes

LLM model(s) used

US-hosted models, for full updated list, see https://ampcode.com/modes

LLM retention settings

Minimal Data Retention is available to Enterprise workspaces. Data is not retained beyond the response, with some exceptions for safety, abuse, and other reasons described here: https://ampcode.com/docs/enterprise/minimal-data-retention

LLM data tenancy policy

Amp Server is multi-tenant. Amp-managed model inference uses model-provider services under Amp-managed provider accounts. See https://ampcode.com/security#data-security-retention for more information.

LLM data residency policy

Amp-managed Slack inference currently uses model-provider infrastructure in the United States. See https://ampcode.com/security#infrastructure-and-service-providers for more information.

Certifications & compliance

Security