No Slack Notification - Background Agent

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

No Slack Notification received after successful completion of the background agent

Steps to Reproduce

  • Start a long running agent

Expected Behavior

Get a notification (the notification setting is enabled and slack connected to my account)

Operating System

Windows 10/11
MacOS
Linux

Version Information

No version

Does this stop you from using Cursor

No - Cursor works, but with this issue

IDK if this is relevant but I connected my slack account while the background agent was running already. Maybe because of that?

3

Hey, thanks for the report.

Good point about connecting Slack while the agent was already running. That’s probably why you didn’t get a notification for that run. The agent likely didn’t pick up the Slack connection mid-session.

Can you try starting a new background agent now that Slack is connected and see if a notification comes through? Also, did you start the agent from the web dashboard, from Cursor IDE, or from Slack?

If notifications still don’t show up for new agents, please share the agent URL (something like cursor.com/agents/...) so we can take a look.

4

Hey Dean,

I will try that and let you know. I started the Background agent through the web dashboard.

5

Now I launched a new background agent (long running): bc-b08e0085-775d-4a73-a4a7-49c654b63d1c

This time I was not notified upon completion to approve the plan it built. I will check if the agent itself will also not send a notification upon completion of the code.

6

@deanrie Still not working upon completion of the agent: bc-65f93284-5a1c-4568-b7bb-c77226f25730

I’ve started the agent via the web with a long running grind agent.

7

Thanks for the extra info, I shared it with the team.

A couple quick questions while we wait:

  • Which Slack workspace are you expecting the notifications in, are they DMs from the Cursor bot or in a channel?
  • Please check that the Cursor bot isn’t muted in Slack. Sometimes Slack hides bot notifications if they’re in the Muted section.

I’ll let you know as soon as I hear back from the team.

9
  • Actually I don’t know as I had no choice during the setup to say if I get them via DM or in a channel. While setting up, I just connected to my slack workspace without specifying any channel
  • I just checked - The bot is not muted

Thank you in advance

10

I just got a notification now. With this one it worked: bc-a508c8b0-efec-46c6-a069-cf398da9d951

1 Like
11

@deanrie I just found out it is because of the long running agents. They do not trigger a notification but the normal agents do.

13

Great diagnostic work, thanks for running an A/B test with different agent types. That’s a really valuable finding.

For now, the workaround is to check the status of long-running agents in the dashboard, but I get that it’s not convenient for long tasks.

1 Like
15

Hello,

Some more information - As well when starting a Background Agent via GitHub Comments, it does not trigger a Slack Notification when completing: bc-308493ea-8e3b-4ade-8e96-7be25f573db7

Best regards

17

Hey @gilles!

Currently, Slack completion notifications (sent as a DM from the Cursor bot) only fire for agents started from the website in the standard (non-long-running) mode. Long-running (grind) agents and GitHub-initiated agents don’t trigger the Slack DM notification upon completion.

Probably a good time for us to evaluate why that is and if it still makes sense. Will take it to the team!

1 Like