# Slack mentions should wake an agent the same way Cursor already does **URL:** \ **Category:** Feature Requests\ **Tags:** slack, automations, cloud-agents\ **Created:** [September 8, 2026, 1:15pm UTC](https://forum.cursor.com/t/slack-mentions-should-wake-an-agent-the-same-way-cursor-already-does/171036 "2026-09-08T13:15:23Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Joe\_LK](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/joe_lk/32/124132_2.png) [@Joe\_LK](https://forum.cursor.com/u/Joe_LK)\ **Post date:** [September 8, 2026, 1:15pm UTC](https://forum.cursor.com/t/slack-mentions-should-wake-an-agent-the-same-way-cursor-already-does/171036/1 "2026-09-08T13:15:23Z")
### Feature request for product/service Cloud Agent (GitHub, Slack, Linear,…) ### Describe the request REALLY NEED THIS. I don’t want another listener I have to keep alive. I want Slack to wake my agent the same way Cursor already wakes automations from Slack. What we have now is a stack of our own pieces. A socket, a webhook routine, wake jobs, and a 5-minute poll as backup. That only works while a process stays running on the agent’s computer. When the computer refreshes, the process dies and mentions sit unseen until someone notices. Last night a teammate @mentioned our Pepe Silvia bot at 1:32 AM CT and got nothing. The official Slack connector is connected and works for search and sending as me. That is not the same thing. It does not wake the agent when someone mentions the bot in a private work channel. What I’m asking for: The same Slack event path Cursor already has, for an agent: A mention or DM of the agent bot wakes that agent immediately No socket, webhook routine, wake job, or poll that we have to keep running Survives a computer refresh Replies as the agent bot, not as my user account Works in private channels, once the app is invited If that means connecting Slack as a channel on the agent, and inviting the app into #bcp-work and #brc-work, tell me the exact step and I’ll do it. Right now Pepe’s Slack channel is only a name on file. Mentions never open the chat. Happy to test one mention after it’s wired and confirm it wakes the agent with nothing else running. THANK YOU! ---
**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\ **Post date:** [September 8, 2026, 4:34pm UTC](https://forum.cursor.com/t/slack-mentions-should-wake-an-agent-the-same-way-cursor-already-does/171036/5 "2026-09-08T16:34:36Z")
@Joe_LK I think you’re looking for an Automation like described here! > [@Subagent enabled chatops in Slack](https://forum.cursor.com/t/subagent-enabled-chatops-in-slack/170577/5): > > Hey @bgalvao, thanks for the suggestion! You can get most of this today without a custom Slack app. The no-code path is an [Automation](https://cursor.com/docs/cloud-agent/automations) with a Slack trigger. Create one automation per “subagent” (for example “ML classifier”), point it at your monorepo, write the instructions your ML engineers want it to follow in the prompt, and set the Slack trigger to your channel with a message filter like /ml-classifier. Leave the trigger open to anyone in the channel, and non-technical teammates can post /ml… And, we are working on an easier way to build bots like this. ---
**Author:** ![Joe\_LK](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/joe_lk/32/124132_2.png) [@Joe\_LK](https://forum.cursor.com/u/Joe_LK)\ **Post date:** [September 8, 2026, 7:05pm UTC](https://forum.cursor.com/t/slack-mentions-should-wake-an-agent-the-same-way-cursor-already-does/171036/7 "2026-09-08T19:05:43Z")
Thanks, that helps. The Slack trigger on a Cloud Agent is a different job from what I’m after. Staff talk to a named Grok Bot in Slack, including people who don’t have Cursor. They @mention that bot in a private work channel. I need that mention to wake that bot and have it reply as itself. No repo, no PR, no slash command, and nothing I have to keep running. What you described (one automation per agent, `/command` or `@Cursor`, open a PR) doesn’t cover that. The line about named agents you can address directly in Slack is the one we need. Happy to test a mention in a private channel once that exists. thank you ---
**Author:** ![Mark\_Molina](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mark_molina/32/121666_2.png) [@Mark\_Molina](https://forum.cursor.com/u/Mark_Molina)\ **Post date:** [September 21, 2026, 7:54pm UTC](https://forum.cursor.com/t/slack-mentions-should-wake-an-agent-the-same-way-cursor-already-does/171036/9 "2026-09-21T19:54:23Z")
+1 — this would be especially useful for Grok Bots / specialist agents. I’d love a Claude Tag–style Slack experience: @-mention a specific bot from a channel or thread and have it wake and reply there, instead of only talking to agents in the Grok Bot desktop app. Mapping Slack mentions to particular agents (when you run several) would make this much more usable day to day.