Cursor BDK's cursor-grokbot-agents extension lets local agents consult Grok Bot

Background

Until now the only documented way for your own code to start a Grok Bot run was a routine's webhook trigger. It had no callback, and the result only showed up in the bot's chat. Cursor's Bot Development Kit (BDK, npm @cursor/bdk) now ships an official cursor-grokbot-agents extension. It lets a local BDK agent consult Grok Bots on the same Cursor account and bring their replies back into the current conversation.

How it works

The extension adds four tools: grokbot__ask, check, interrupt and list. The bot keeps its own conversation, memory and tools, but it cannot see the BDK conversation, so each message must stand on its own. The agents list is a name allowlist, not an existence check, so a misspelled name can create an empty bot. All callers share the same account's bot memory.

Numbers

Cursor has published no benchmarks or latency figures. Public npm data: the package was first published on Sep 22, has had 22 releases as of Oct 13 (latest 0.2.23), and was downloaded about 9.4k times last week. Its license is the proprietary Cursor SDK License, not an OSI open-source license.

Getting started

It needs Node 22.13 or newer. Run bdk init ./grokbot --template grokbot-agents and authenticate with CURSOR_API_KEY or bdk login. The flagged post says Claude Code and Codex can message Grok Bot once the extension is installed. Cursor's docs only cover BDK agents and don't mention native Claude Code or Codex support, so treat that as a community workflow.