Slack app posts "Link Account" onboarding reply to unlinked users even when the automation run succeeds

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

I have a cursor automation that triggers on every message in a channel. When the automation decides there is nothing to do, it should exit silently. For messages from me, that works. When the message is from a Slack user without a linked Cursor account, the automation triggered and completed correctly — the agent classified the message as no-action and intentionally posted nothing (run: https://cursor.com/agents/bc-59c8b9e4-5f87-500e-bc26-fe370b0b4535). But the Cursor Slack bot separately replied in her thread: “:waving_hand: Hey… You can launch Cursor agents directly from Slack. Click the Link Account button above to get started.”

Impact: this is a business intake channel monitored by an automation; every message from non-Cursor users (sales/CS staff who will never have Cursor accounts) gets onboarding spam. Our PM replied “stop” to the bot — it’s eroding trust in the automation. Looks related to [Slack Integration Spamming intro message] and [Automations Slack only working for some users].

Setup: Slack automation “#ask-s4b-epd triage V1” (cursor.com/automations/85bd4697-418c-4da5-92a9-626c62616869), trigger = Any Message / from Anyone / in 2 channels, owner account linked.

Steps to Reproduce

  1. set up automation that is triggered by any message from anyone in a slack channel, have the automation exit silently
  2. a slack user without a cursor account messages in the channel to trigger the automation

Expected Behavior

Expected: when a message merely triggers an automation, the author shouldn’t be prompted to link an account — they aren’t trying to use Cursor. The onboarding interstitial should only appear when someone explicitly @-mentions Cursor.

Operating System

Other

Version Information

Cursor automation triggered by slack message

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hi @Lily_Guo!

I believe you also shared this with us via e-mail support and I confirm a bug report has been raised for this issue. Thanks for reporting!