Marketplace › Setup

Grok Bot Setup

Letting Claude Code hand tasks to Grok Bot through a webhook

There's no public API for driving bots, so Dan Mercede uses the documented door: a routine with a webhook trigger, which a coding agent calls to start a run. Results come back as files on his PC through local execution, and his open-source MIT sender will never send the same request twice. He's candid about the cost: getting results back automatically needs local execution set to Always allow, which covers every bot, so a leaked key or a prompt-injected page could run commands on your machine. His optional extras (driving the app over a debug port and reading its local cache) rely on undocumented internals that can break with any update. They also sit close to Cursor's terms on reverse engineering and extracting data from the service, so the webhook and file lanes are the safer part to copy.

1. Create a dedicated bot whose webhook routine says the request body can never override its rules.
2. Keep the webhook URL and key in a secret manager, and treat the key like a password.
3. If you only need to fire off tasks, leave local execution on Never allow and read results in the bot's chat.
4. Don't automatically resend after a timeout or unclear reply: check the bot's chat first so one task doesn't run twice.

Submit yours