Slack APIBreaking changehigh

Slack sends system notices as USLACK, not Slackbot, from Jun 17, 2026

Detected
Oct 16, 2026
Effective
Jun 17, 2026(took effect 152 days ago)
Confidence
92%

What changed

Slack system notifications are now delivered from a new 'Slack' system user (USLACK) instead of Slackbot. Apps that filter events or messages by Slackbot's user ID or username to identify system notifications will break.

What to do

Update any integration logic that filters by Slackbot's user ID or checks the username field for 'Slackbot' to instead handle the new 'Slack' system user (USLACK). Additionally, note that the assistant_view experience is being deprecated in February 2027 — begin migrating to agent_view using the provided migration guide.

Affected

model: USLACK (Slack system user)endpoint: chat.postMessagemodel: message.immodel: assistant_viewendpoint: assistant.threads.setStatusendpoint: assistant.threads.setTitleendpoint: agents.sessions.setStatusendpoint: agents.sessions.rename

Source: api.slack.com (Slack's own page, checked by Breakwatch)

Is your code affected?

Search your repositories for the Slack SDK and the names above:

npm: @slack/web-apinpm: @slack/boltpip: slack_sdkruby: slack-ruby-clientgo: github.com/slack-go/slackphp: jolicode/slack-php-apijava: com.slack.api:slack-api-client

Or let Breakwatch do it: connect a repo and see which files call Slack, then get the next change as an alert pointing at those files. Check a repo free

Get Slack API changes by email

Once a week: the breaking changes and upcoming deadlines for Slack, each linked to the vendor's own page. Free, no account. One-click unsubscribe.

More Slack API changes

Every Slack API change →