Changelog Update

Slack MCP Improvements: Reactions, Status Updates, and Optional "Sent by Agent" Footer

🎯 What is it?

Your agents can now do more when working through the Slack integration. They can add and remove emoji reactions, update Slack status, and—when an admin allows it—send messages without the "sent by agent" footer that normally appears with personal authentication.

💡 Why is it useful?

Until now, these were hard limitations of the Slack integration: agents couldn't react to messages, change status, or send messages that looked fully native. These additions let your agents interact in Slack in a more natural way, and give you finer control over how agent-sent messages appear to your teams.

⚙ How does it work?

Reactions and status updates are available to everyone out of the box. The "sent by agent" footer can be turned off on a per-message basis, but only if an admin has enabled that option for your workspace—so you stay in control of transparency.

✨ Concrete Use Cases

Here's how you could use it:

• Acknowledging messages: An agent monitoring a support channel can add a ✅ reaction once it has picked up and handled a request, giving your team an instant visual cue.

• Signaling availability: An agent can update a user's Slack status (for example, "In a meeting" or "Focusing") based on calendar events or workflow triggers.

• Cleaner notifications: For internal broadcast messages where the footer adds noise, an admin-approved agent can post updates that read more naturally to recipients.

📈 Benefits for you

Agents feel more like real teammates inside Slack, interactions are smoother, and admins keep control over both transparency and how agent messages are presented.

🚀 How to access it?

Reactions and status updates are available now to everyone using the Slack integration—no setup needed. To allow users to remove the "sent by agent" footer, an admin needs to enable the corresponding toggle in your workspace settings first.