ref(slack): Remove assistant:write OAuth scope from Slack integration#116567
Merged
alexsohn1126 merged 1 commit intoJun 1, 2026
Merged
Conversation
The assistant feature has been removed from the Slack app, so we no longer need to request the assistant:write scope during OAuth installation. Existing integrations that already have this scope will continue to work, but new installations will not request it. Co-authored-by: Alex Sohn <alexsohn1126@users.noreply.github.com>
github-actions
Bot
added
the
Scope: Backend
cleptric
approved these changes
Jun 1, 2026
afsuyadi
pushed a commit
to afsuyadi/sentry
that referenced
this pull request
Jun 2, 2026
…getsentry#116567) <!-- CURSOR_AGENT_PR_BODY_BEGIN --> This PR removes the `assistant:write` OAuth scope from the Slack integration's requested scopes during installation. ## Context The assistant feature has been removed from Sentry's Slack app, so we no longer need to request the `assistant:write` scope when users install the integration. ## Changes - Removed `SlackScope.ASSISTANT_WRITE` from `identity_oauth_scopes` in `SlackIntegrationProvider` ## Behavior - **New installations**: Will not request or receive the `assistant:write` scope - **Existing installations**: Will continue to work with their existing scopes. The code that uses assistant functionality (`set_thread_status`, `set_suggested_prompts`) already has defensive error handling and will gracefully handle missing scopes. ## Testing The existing test suite covers: - OAuth scope verification in `test_integration.py::test_initialize_pipeline` - Defensive behavior when the scope is missing (tests set scopes in metadata) Related to: #inc-2211 <!-- CURSOR_AGENT_PR_BODY_END --> [Slack Thread](https://sentry.slack.com/archives/C0B7AMW5XL6/p1780319812860829?thread_ts=1780319812.860829&cid=C0B7AMW5XL6) <div><a href="https://cursor.com/agents/bc-d59dd21c-3ae5-5e0e-9638-f805395d6efa"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a href="https://cursor.com/background-agent?bcId=bc-d59dd21c-3ae5-5e0e-9638-f805395d6efa"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> </div> Co-authored-by: Cursor Agent <cursoragent@cursor.com> Co-authored-by: Alex Sohn <alexsohn1126@users.noreply.github.com>
![https://cursor.com/assets/images/open-in-web-dark.png"><source](https://cursor.com/assets/images/open-in-web-dark.png"><source){kind=link}
![https://cursor.com/assets/images/open-in-web-light.png"><img](https://cursor.com/assets/images/open-in-web-light.png"><img){kind=link}
![https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a](https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a){kind=link}
![https://cursor.com/assets/images/open-in-cursor-dark.png"><source](https://cursor.com/assets/images/open-in-cursor-dark.png"><source){kind=link}
![https://cursor.com/assets/images/open-in-cursor-light.png"><img](https://cursor.com/assets/images/open-in-cursor-light.png"><img){kind=link}
![https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> </div](https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> </div){kind=link}
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR removes the
assistant:writeOAuth scope from the Slack integration's requested scopes during installation.Context
The assistant feature has been removed from Sentry's Slack app, so we no longer need to request the
assistant:writescope when users install the integration.Changes
SlackScope.ASSISTANT_WRITEfromidentity_oauth_scopesinSlackIntegrationProviderBehavior
assistant:writescopeset_thread_status,set_suggested_prompts) already has defensive error handling and will gracefully handle missing scopes.Testing
The existing test suite covers:
test_integration.py::test_initialize_pipelineRelated to: #inc-2211
Slack Thread