Team Bot can't hand work to other Team Bots when a teammate (not the owner) asks in Slack, but the same handoff works in the Grok Bot app

Support Bug Reports
,
1

Where does the bug appear (feature/product)?
Something else… (Grok Bot Team Bots in Slack: bot-to-bot handoff)

Describe the Bug
When a teammate (not the bot’s owner) asks a coordinator Team Bot in Slack to pass work to another Team Bot, the direct handoff is always refused. The same handoff works when that teammate asks in the Grok Bot app, and when the owner asks in Slack.

Steps to Reproduce

  1. In a Slack workspace, install several Team Bots, each as its own Slack app. One acts as the coordinator and hands work to another.
  2. A teammate whose Slack account is linked to Cursor, and who has added both Team Bots to their Grok Bot sidebar, @mentions the coordinator in a channel with a task meant for the other bot.
  3. The coordinator tries a direct handoff to the other bot, by name and by agent ID.

Expected Behavior
The handoff goes through and the other bot starts the task, the same as when the teammate asks in the Grok Bot app or the owner asks in Slack.

Actual Behavior
The handoff is refused with roughly “none of the requester’s own agents matched” or “that bot isn’t one of the agents I can reach from your account”. It fails every time, by name and by ID.

Operating System
MacOS

Version Information
Grok Bot desktop app: 0.70.2
Slack desktop app: 4.52.178

For AI issues: which model did you use?
N/A, this is a handoff and permissions issue, not a model output problem.

For Background Agent issues, also post the ID
N/A for the main bug. In the related problem below, the target bot’s cloud agent run was refused before it started.

Additional Information

  • Teammates who ask in the Grok Bot app don’t hit this.
  • Related: if the coordinator @mentions the target bot in Slack instead, that bot replies, but its cloud agent run is refused, because the request comes from the coordinator’s bot account, which has no Cursor account.
  • A teammate tagging the target bot themselves works, but that skips the coordinator’s routing and tracking.

Does this stop you from using Cursor?
No. Cursor works, but with this issue.

2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

7

Hey @Interbase_Resources, thanks for the clear write-up!

This is how Team Bots work in Slack today, not something in your setup. In Slack, a Team Bot acts only for the person asking, so it can hand a teammate’s request only to Bots that teammate owns, not to Team Bots they’ve added. The Grok Bot app includes added Team Bots, which is why it works there (and for you in Slack, since you own them all). The bot-to-bot @mention case is expected too: a message from another bot can’t start work on anyone’s account.

For now, teammates can run coordinated handoffs from the Grok Bot app. We’ve let the team know you’d like Slack to work the same way.

9

Thanks for the clarification!

It would be great to have this supported in Slack as well. In a multi-agent setup, the coordinator should be able to delegate tasks to other Team Bots that the requester has access to, even if they don’t own those bots.

Having to switch to the Grok Bot app for coordinated handoffs breaks the workflow, especially when Slack is the main interface for the team.

Is there a plan to support this in Slack, perhaps by allowing handoffs to Team Bots that the requester has added or been granted access to?