Follow ups not allowed by teammates in slack when team follow-ups enabled

[blusenhop]

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

When automations run and post back in slack, teammates who did not create/trigger the automation cannot follow up to the cloud agent.

Steps to Reproduce

1. create a team owned automation that posts into slack
2. ensure team follow ups are enabled in team settings
3. Trigger an automation run that posts into slack with an executed automation run
4. have a teammate who does not own/create the automation attempt to @cursor in the slack thread to add a follow up
5. Receive “Looks like this cloud agent doesn’t belong to you, so you can’t add a follow-up.” error message.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Automations + Slack

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

[blusenhop]

[mohitjain (Mohit)]

Hi Blake!

Thank you for the detailed bug report and steps to reproduce. This is a known issue where teammates are blocked from following up on cloud agents created by automations (or service accounts), even when Team Followups is enabled in the dashboard settings.

Our engineering team is aware of the problem and is tracking a fix. The root cause involves the follow-up permission check not correctly honoring the Team Followups setting for agents created by automations on behalf of the team.

In the meantime, the workaround mentioned in the error message is the best option: have the teammate start a new thread with @Cursor agent to launch their own agent.

I’ve added your report to the internal tracking issue so the team has visibility into this specific automations + Slack scenario. I don’t have an ETA to share, but this is something we’re working to address.

Best,
Mohit

[Noe (Noé)]

I’m getting this same issue as well. Is this fix in the works?

[mohitjain (Mohit)]

This is still a known issue that our engineering team is tracking. I don’t have a specific ETA to share yet, but I’ve added your report to the internal tracking to help with prioritization!

In the meantime, the best workaround is to have the teammate start a new thread with @Cursor agent instead of replying in the automation’s thread.

[Eike_Sturmer (Eike Stürmer)]

Having the same problem as of today. It was working for the same users beforehand