Package
@slack/web-api
Description
Given the deprecation of rtm.start with its SelfPrefs, there is no way to fetch the user's muted channels/conversations anymore.
When developing AI agents, knowing whether a conversation is muted by the user is an important signal. For example, it can be used to ignore channels or reduce their priority when asking an AI agent something like "what new messages are important to me", or when proactively reacting to messages, deriving tasks, etc. in user workflows.
Not knowing what conversations are muted results in a different user experience in the Slack app vs. when interacting with Slack using AI agents on behalf of the user.
There should be a way to fetch a user's muted conversation list and/or filter conversation lists by muted status + return an isMuted flag.
Alternatives Considered
rtm.start is deprecatedusers.prefs.get is not available to Slack apps, only Slack clients
Package
@slack/web-api
Description
Given the deprecation of
rtm.startwith itsSelfPrefs, there is no way to fetch the user's muted channels/conversations anymore.node-slack-sdk/packages/web-api/src/types/response/RtmStartResponse.ts
Line 1737 in 909b5bd
When developing AI agents, knowing whether a conversation is muted by the user is an important signal. For example, it can be used to ignore channels or reduce their priority when asking an AI agent something like "what new messages are important to me", or when proactively reacting to messages, deriving tasks, etc. in user workflows.
Not knowing what conversations are muted results in a different user experience in the Slack app vs. when interacting with Slack using AI agents on behalf of the user.
There should be a way to fetch a user's muted conversation list and/or filter conversation lists by muted status + return an
isMutedflag.Alternatives Considered
rtm.startis deprecatedusers.prefs.getis not available to Slack apps, only Slack clients