Skip to content

Update Slack integration docs for better security clarity #1279

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 25, 2025
Merged

Update Slack integration docs for better security clarity #1279

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/integrations/slack.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,11 +75,12 @@ Codegen only responds when tagged or messaged directly. Use these approaches to
- **Direct Messages:**

- Responds to any DM sent to the Codegen integration for Slack
- Has visibility into previous messages in the conversation (not just threaded replies)
- Codegen only sees messages in the direct message conversation where it has been invited
- This provides a more natural conversation experience as many users don't thread messages in DMs

- **Channel Messages:**
- Responds to any message that @mentions Codegen in channels where the integration for Slack is installed
- Codegen only sees messages in threads that it has been invited into
- Only has visibility into the local context of the thread/conversation
- Sending subsequent messages within a thread routes to the same agent (tag `@codegen` to trigger)
- New messages to `@codegen` in an active thread will interrupt the agent if it's currently working
Expand Down