Add a verified thread unsubscribe command - #137
Closed
dwaxe wants to merge 1 commit into
Closed
Conversation
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
1 participant
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.
Adds
agent-slack thread unsubscribe <message-url>to stop notifications from one exact Slack thread.The command requires browser-session auth and an exact HTTPS Slack message URL. It preserves the current
last_read, supports Enterprise Grid by routing subscription calls through the organization workspace after confirming the workspace and organization credentials belong to the same Slack user and organization, verifies that the thread is no longer subscribed, and treats repeat runs as an idempotent no-op.Slack doesn’t expose a public thread-unsubscribe API, so the unsupported endpoint is isolated behind a narrow adapter and fails closed if the response shape is unexpected.