Slack Bot post does not trigger cloud agent

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

We have a slack alert system setup with our backend. If a certain feature fails, it send a bot message to a slack public channel.

Also a Cursor cloud agent setup with that channel. so if any alert message post from backend, agent auto pick the message and based on the alert information, make changes on codebase and Create PR on github.

It was working perfectly. But suddenly its stop working from last week. Based on my R&D, it seems not working because of slack bot message. Same Agent is triggering perfectly when I pasting the same alert from my slack account manually. But not working with automated slack bot message.

Steps to Reproduce

To reproduce, needs to setup cloud agent with slack bot message system.
And need to setup a trigger system like I explain from bug description.

Expected Behavior

Cloud agent should trigger even from bot message. Like it was already working before.

Operating System

MacOS

Version Information

Version: 3.2.11
VSCode Version: 1.105.1
Commit: e9ee1339915a927dfb2df4a836dd9c8337e17cc0
Date: 2026-04-24T14:36:47.933Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.4.0

For AI issues: which model did you use?

Composer 2. But probably is not model specific. Issue is happening for other models too.

Does this stop you from using Cursor

Yes - Cursor is unusable

5

Hey, thanks for the detailed report. This is a known regression. After backend changes around April 24, Slack automations only trigger correctly for the automation creator, and bot messages aren’t processed at all. We’re already tracking this internally, but I can’t share an ETA for a fix yet.

For context, there’s a parallel thread with the same symptom: Automation with Slack trigger no longer replying to any users but automation creator

For now, the only workaround is the one you already found: manually reposting from the automation creator’s user account. We’ll post an update in that thread as soon as we have one.