Slack

Category: communications

5 changes tracked

Monitored sources:

changelog · every 6h

SDK packages:

@slack/web-api@slack/boltslack_sdkslack-ruby-clientgithub.com/slack-go/slackjolicode/slack-php-apicom.slack.api:slack-api-client

Last polled: 10/7/2026, 6:00:03 PM

Change History

breakinghigh92% confidence

Slack system notifications (channel membership changes, User Group updates, Slack Connect alerts, retention policy notices) 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.

Migration: Update any logic that filters by Slackbot's user ID or checks the username field for 'Slackbot' to instead handle the new 'Slack' system user (USLACK). Also update any chat.postMessage integrations that expected system notifications to route through Slackbot.
model:USLACK (new Slack system user)param:username (Slackbot → Slack)endpoint:chat.postMessagemodel:message.user (system notification sender)

10/7/2026

Effective: 6/17/2026

deprecationhigh92% confidence

The `assistant_view` (Assistant messaging experience) will be deprecated in February 2027, replaced by `agent_view` (Agent messaging experience) and a new Agent Sessions API. Additionally, system notifications are now delivered by a new 'Slack' system user (USLACK) instead of Slackbot, which is an immediate breaking change for apps filtering by Slackbot's user ID.

Migration: 1) Migrate from `assistant_view` to `agent_view` using the migration checklist; replace `assistant.threads.setStatus` and `assistant.threads.setTitle` with `agents.sessions.setStatus` and `agents.sessions.rename`. 2) Update any integrations that filter messages by Slackbot's user ID or username to handle the new 'Slack' system user (USLACK) immediately.
model:assistant_viewmodel:agent_viewendpoint:assistant.threads.setStatusendpoint:assistant.threads.setTitleendpoint:agents.sessions.setStatusendpoint:agents.sessions.renamemodel:USLACKBOT (Slackbot system user)model:USLACK (Slack system user)

10/5/2026

Effective: 2/1/2027

breakinghigh92% confidence

Slack system notifications are now delivered from a new 'Slack' system user (USLACK) instead of Slackbot, and the assistant_view messaging experience will be deprecated in February 2027 in favor of the new agent_view. Apps filtering events by Slackbot's user ID or username for system notifications must update their logic to handle the new USLACK sender.

Migration: Update any integrations that filter by Slackbot's user ID or username for system notifications to use the new USLACK system user. For agent apps using assistant_view, follow the migration guide to move to agent_view before February 2027. Replace assistant.threads.setStatus and assistant.threads.setTitle calls with agents.sessions.setStatus and agents.sessions.rename.
model:USLACK (new system user)endpoint:assistant.threads.setStatusendpoint:assistant.threads.setTitleendpoint:agents.sessions.setStatusendpoint:agents.sessions.renameparam:assistant_viewparam:agent_viewmodel:app_context_changed eventmodel:agent_session_stopped event

9/25/2026

Effective: 2/1/2027

breakinghigh88% confidence

Slack system notifications are now delivered from a new 'Slack' system user (USLACK) instead of Slackbot, affecting apps that filter events or messages by Slackbot's user ID or username. Additionally, the assistant_view messaging experience is being deprecated in February 2027, replaced by the new agent_view and Agent Sessions API.

Migration: Update any integrations that filter by Slackbot's user ID or check the username field for 'Slackbot' to handle the new USLACK system user. For agent apps using assistant_view, begin migrating to agent_view and the Agent Sessions API (agents.sessions.setStatus, agents.sessions.rename) before February 2027.
model:USLACK (new Slack system user)endpoint:assistant.threads.setStatusendpoint:assistant.threads.setTitleendpoint:agents.sessions.setStatusendpoint:agents.sessions.renameparam:assistant_viewparam:agent_viewmodel:app_context_changed eventmodel:agent_session_stopped event

9/16/2026

Effective: 6/17/2026

breakinghigh92% confidence

Slack system notifications are now delivered from a new 'Slack' system user (USLACK) instead of Slackbot, affecting any integrations that filter events by Slackbot's user ID or username. Additionally, Bolt for JS v5 and Node Slack SDK major version bumps introduce breaking changes including removal of Workflow Steps from Apps, raised minimum Node.js version to 20, and removal of agent/clientTls options.

Migration: Update integrations that filter by Slackbot's user ID or username to handle the new USLACK system user. For Bolt for JS v5, follow the v4-to-v5 migration guide: remove Workflow Steps from Apps usage, upgrade to Node.js 20+, and replace agent/clientTls options with the new dispatcher option. For @slack/socket-mode, @slack/web-api, and @slack/webhook, follow their respective v2→v3 and v7→v8 migration guides.
model:USLACKBOT (system user / Slackbot)model:USLACK (new Slack system user)param:agent (AppOptions - removed)param:clientTls (AppOptions - removed)model:Workflow Steps from Apps (removed in Bolt for JS v5)model:@slack/socket-mode v3model:@slack/web-api v8model:@slack/webhook v8

8/20/2026

Effective: 6/17/2026

Get alerts when Slack changes affect your code

Connect your GitHub repos and Breakwatch will map your Slack usage and alert you about relevant changes.

Get started for free