Slack changed its API changelog

===================================================================
--- before
+++ after
@@ -8,8 +8,44 @@
 RSS
 
 Atom
 
+We're rolling out a wave of updates to agents on Slack, along with an important heads-up about the road ahead for the Assistant messaging experience.
+
+AGENT UPDATES AND THE DEPRECATION OF ASSISTANT_VIEW
+
+The Assistant messaging experience (assistant_view) will be deprecated in February 2027. The assistant-related methods that power it are being replaced by a new set of API methods: the Agent Sessions API. Agent sessions let users manage their conversations with your agent in one place, with a status, a title, and a stop button. The agents.sessions.setStatus and agents.sessions.rename API methods replace the assistant.threads.setStatus and assistant.threads.setTitle API methods, respectively. For now, your existing calls keep working through a compatibility bridge. See the Agent sessions guide to get started.
+
+The Agent messaging experience (agent_view) is already available, and we recommend moving to it now. If your app still uses assistant_view, follow the migration guide to move to the new experience. Read more in the guide to developing agents.
+
+WHAT'S NEW FOR AGENTS
+
+Alongside this announcement, we're releasing a set of improvements to the agent experience:
+
+ * Upgraded Tools tab: a newly renamed and revamped Agents & Tools tab helps users find popular agents with a new landing page.
+ * Improved thread experience: including multi-agent stacking, thread naming, a revamped thinking UI, and a native stop button for agent streams. When a user stops your agent, your app receives an agent_session_stopped event.
+ * Plan and Task card block updates: UI refinements to the plan and task card blocks agents use to show their work.
+ * Marketplace data in the About tab: an agent's Marketplace data now appears in its About tab.
+ * Agent sessions in the sidebar: A new sidebar with pin / archive / unread and live updates.
+
+An agent can answer a question in a thread, but some tasks become bigger than a single question. A coding agent may need to implement a change, share a prototype, and iterate on it. A research agent may need to gather information and work through decisions with the people involved. This kind of work needs more than a single response.
+
+Slack Code is how agents and people work together to build with AI in Slack, creating dedicated channels for more involved work. A channel is created from an existing conversation, context is carried forward, and agents and collaborators have a shared, visible place to work.
+
+Within a session, agents can publish artifacts for people to oversee and iterate on:
+
+ * Code diffs, so people can review what changed
+ * Block Kit views, for structured interactive experiences
+ * HTML previews, for prototypes and generated interfaces
+ * Canvases, for longer-form content and collaboration
+
+The work becomes multiplayer: teammates can join channels, review work, add context, and help make decisions, all while collaborating in the same session and with the same artifacts. Your agent manages the lifecycle, creating a channel when a task warrants one, sharing updates as the work progresses, and closing the session once the work is complete.
+
+Read on to learn more:
+
+ * Slack Code: where your team and agents build together
+ * Build with AI as a team using Slack Code
+
 We're excited to introduce the Slack MCP and Skills Plugin for AI tools, which bundles a set of skills that help you develop on the Slack platform alongside the Slack MCP Server. The plugin is currently available for Claude Code and Cursor.
 
 Installing the plugin sets up two things: