Slack follow-up to teammate cloud agent fails with “this cloud agent doesn’t belong to you” even though Team Followups = On all team member agents

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

We’re seeing a regression in the Slack integration for Cloud Agents.

Summary

A teammate cannot send a follow-up in an existing Slack thread to a cloud agent started by another teammate, even though our Cursor team setting for Team Followups is set to On all team member agents.

Instead, Slack shows:

Looks like this cloud agent doesn’t belong to you, so you can’t add a follow-up. Try launching your own agent instead with @Cursor agent or start a new thread. If your team wants this enabled, ask a team admin to turn on Team Followups in the cloud agents dashboard settings.

Why this looks wrong

In Cursor Dashboard → Cloud Agents → Security, our setting is already:

  • Team Followups: On all team member agents

So based on the docs, teammates on the same team should be able to follow up on each other’s agents.

Also, this worked for us before and the setting was not changed.

Example thread

This is one example of the behavior:

  • Birte asked: “How many impressions did we have on Meta in NL from 13.04.26 to 19.04.26?”
  • Cursor replied with the analysis
  • Birte then replied: “Just give me the number of impressions without further explanation”
  • Instead of accepting the follow-up, Cursor responded with the ownership error and suggested enabling Team Followups, but Team Followups is already enabled for all team member agents

Actual behavior

Cursor rejects the follow-up and behaves as if Team Followups were disabled.

Questions

  • Is there a known regression in Slack follow-ups for Cloud Agents?
  • Do Team Followups permissions only apply to newly created agents in some cases?
  • Is there any known issue specific to Slack threads vs web/desktop follow-ups?

This is an issue as of yesterday

Steps to Reproduce

  1. User A starts a cloud agent in Slack with triggered by an automation for every new message in a channel
  2. Cursor responds in the thread
  3. User B, who is on the same Cursor team, replies in the same Slack thread with a follow-up
  4. Cursor returns the ownership error above instead of attaching the follow-up to the existing agent

Expected Behavior

Since Team Followups = On all team member agents, any teammate on the same Cursor team should be able to add a follow-up to the existing Slack agent thread.

Operating System

MacOS

Version Information

Version: 3.1.17 (Universal)
VSCode Version: 1.105.1
Commit: fce1e9ab7844f9ea35793da01e634aa7e50bce90
Date: 2026-04-19T19:33:58.189Z
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?

5.4 extra high

For AI issues: add Request ID with privacy disabled

serverGenReqId_8da6638c-c58f-4f5f-ae13-290782397a29

Additional Information

It is a problem as of yesterday, but could already have been happening over the weekend

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

7

Hey Eike!
I see you also reported this in this earlier thread, so apologies you’re still running into it.

This is a known bug where the follow-up permission check doesn’t correctly honor the Team Followups setting for agents created by automations, even when it’s set to “On all team member agents.” Our engineering team is aware and tracking a fix.

The intermittent aspect you’re describing (working before, then breaking) is helpful context and I’ve flagged it internally.

For now, the best workaround is to have teammates start a new agent with @Cursor agent in a new Slack thread rather than replying in the automation’s thread. I know that’s not ideal, but it’s the most reliable path until the fix ships.