See Cursor Grok Bots
Find your Cursor Grok Bots on the Bots tab of the Sessions page, with each bot's routines, who set it up, and what it spent.
Grok Bots are Cursor's always-on agents. Each bot runs routines, started on a schedule, by a Slack mention or message, by a webhook, or by an email. Cursor bills the bot, not each routine, so Grok Bots don't appear as sessions or scheduled tasks. They have their own Bots tab on the Sessions page.
Who can see this: Admins. See Roles and permissions.
Open the list
Go to Sessions and click the Bots tab. You can also search for "Bots" or "Grok bots" in the app's search.
Use the date range menu in the top right to pick Last 7 days, Last 30 days, or Last 90 days. It sets which requests and spend the rows cover.
While the list loads, the tab says "Loading bots". If your organization has no Grok Bot spend in the range, it says "No bots yet" and "Cursor Grok Bots show here once they run."
Read a row
Each bot is one row, with the Grok logo, the bot's name, and its request count and cost on the right, such as "42 requests | $320.00". A bot with no name in Cursor's audit log reads "Unnamed bot".
Click a row to open it:
- Routines lists each routine with an icon for what starts it, its name, and the trigger: Scheduled, Slack mention, Slack message, Webhook, or Email. A routine Cursor doesn't describe shows a bot icon and no trigger. An Off or Deleted badge means the routine no longer runs. "No routines" means the bot has none. A routine with no name reads "Unnamed routine".
- Who set it up names who created the bot and how many people set up its routines, with their avatars. Click an avatar to open that person's profile. "Unknown" means Cursor's audit log doesn't say.
Two more rows cover spend no named bot can be matched to:
- Sub-agent runs. Opening it says how many runs, and "Cursor doesn't say which bot started them."
- Other bots. Opening it says how many conversations, and "Cursor's audit log doesn't name these bots."
Where the names come from
Bot names, routines, and who set them up come from Cursor's team audit log, read with your Cursor Team Admin API key. Spend comes from Cursor's usage reports, so it shows even when the audit log can't be read. A note at the top of the tab says when names are missing:
| Note | What to do |
|---|---|
| "Bot names and routines appear after the first sync." | Check again later. |
| "Bot names and routines need a Cursor Enterprise team." | Cursor only shares the audit log with Enterprise teams. Spend still shows. |
| "Couldn't sync from Cursor. Bot names and routines may be out of date." | Check again later. |
Troubleshooting
"Couldn't load Grok Bots." Click Try again.
Related
- Grok Bot spend that isn't on a pull request is listed by bot on the Engineering page.
- To record what Grok Bots do inside Cursor, turn on Grok Bot Action Recording. See OpenTelemetry.
- For scheduled tasks on other platforms, see See scheduled tasks.