Cursor's own engineers reportedly run Grok Bot as the orchestrator and call the Cursor Agent CLI from it.

Matthew Berman relays a workflow the Cursor team described to him: a separate bot per project and per workstream, tasks triggered from Slack, and the bot invoking the Cursor Agent CLI and cloud agents rather than driving Cursor directly. Their stated reason is context persistence, claiming the bot holds project context across Notion, email, Slack, and GitHub better than Cursor does alone, and loops on a PR until CI goes green. Matthew Berman Second-hand and unconfirmed by Cursor, so weight it accordingly. If accurate, the company selling the editor runs its own work from a chat bot, which is a hell of a data point for the Antigravity story above.