Matthew Berman Says Cursor's Own Engineers Run Grok Bot as the Orchestrator and Call the Cursor Agent CLI From It, One Bot Per Workstream, Kicked Off in Slack
In a 22-minute video posted 2026-08-20, Berman relays a workflow the Cursor team described to him directly: spin up a separate Grok Bot per project and per workstream, trigger tasks from Slack, and have the bot invoke the Cursor Agent CLI and Cursor cloud agents rather than driving Cursor directly. Their reason is context persistence — they claim the bot holds and carries project context across Notion, email, Slack and GitHub better than Cursor does on its own, and it loops on a PR until CI goes green before merge. The rest of the video is a concrete inventory of his own bots (email triage at 7:30am, email labeling every 30 minutes 8am-7pm, a Fathom meeting-summary poller, a weekly disk cleanup bot that flagged 90GB low-risk and 380GB medium-risk), all fronted by a single 'chief of staff' bot that delegates.
↳ Follow the thread