Can't followup on Cursor Automation co-workers' sessions

[Shahar_Barak]

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

We have various team-wide Cursor Automations that run on a service account user (a fake team member). Until now it worked fine. Now, it seems that you added the option to make a cloud agent session private or public (Team). The Automations’ sessions are now all Private by default and this means that team members can’t view the Automations’ sessions and can’t followup in Slack messages/replies initiated by the Automation to ask followup questions or give the agent further instructions.

Steps to Reproduce

In Cursor, create a team-wide Automation that runs under a service account user (a non-human team member), and configure it to post to Slack.
Trigger the Automation (on its schedule or manually) so it starts a cloud agent session.
Open the session list as a different team member (not the service account).
Note the session’s visibility setting. It is set to Private by default.
As that team member, try to open the session from the list, or from the link in the Automation’s Slack message.
As that team member, reply in the Slack thread of the Automation’s message to ask a followup question or give the agent further instructions.

Expected Behavior

Sessions started by a team-wide Automation are visible to the team (Team visibility), as they were before the Private/Team option was introduced. Team members can view the session and followup in Slack replies.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

not relevant

For AI issues: which model did you use?

not relevant

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

[Colin]

Hey, thanks for the feedback!

You’re right: new cloud agent sessions started by an individual user account now default to Private. Because your Automations run under a team-member account, their sessions are private to that account, so teammates can’t open them or follow up in Slack. There isn’t a team-wide setting to change this default right now.

The workaround is to run the Automations as a service account instead. A team admin can open each Automation, click Share, set Run as to Service account, and set Access to Members can view or Members can edit. Sessions from service-account Automations are visible to the team, so follow-ups work again. More detail is in the Automations docs.

Things to know before switching: usage moves to the team’s usage pool, MCPs or integrations tied to someone’s personal login need to be set up for the service account, and webhook API keys should be regenerated. Sessions that already ran stay Private.

I’m not sure how this change is meant to interact with the “Team Followups” setting and I’m chasing that down. In the meantime, setting the automation to run a service account should let team members follow up.