Grok Bot: no first-class ownership-transfer action (only SendToAgent)

Feature request for product/service

Cursor IDE

Describe the request

Grok Bot has a first-class bot-to-bot message/wake (SendToAgent) but no equivalent first-class action to transfer ownership of work with a durable receipt.

A bot can correctly refuse work it does not own and still lose the work, because the only native inter-bot act is a wake. The ownership change dies in chat.

This is a missing product primitive, not a missing prompt.

Steps to reproduce:

  1. Bot A asks Bot B (Chief) to do structural work B does not own.
  2. B correctly refuses and messages A with SendToAgent.
  3. No durable ownership record exists. A cannot accept, reject, or close on an id.
  4. Local workaround (a shared log or a script) is only used if the bot remembers the path. It is not in the always-visible tool list.

Expected:
A native action at the same practical level as SendToAgent, conceptually TransferOwnership(work, owner, reason):

  • always visible in the tool list (no prior discovery call)
  • writes a durable ownership record with origin, reason, and receipt states (accept / reject / blocked / close)
  • may notify the recipient, without treating the notify as the record
  • applies only to consequential work, not casual bot chat

Local scripts, skills, and MCP connectors are not equivalent.

OS: Linux. Build: Cursor 3.15.6 (Grok Bot 0.16.0) as last known on 15 Aug 2026.

Evidence from this account (15 Aug 2026): three identical Travel structural-write refusals were messages only, zero durable transfer lines.

Related posted thread: Grok Bot: no glanceable working/finishing signal unless the pointer is on the bot icon

This does not stop using Cursor; it works with this issue.

Operating System (if it applies)

Linux