grokbotwiki

Claude Code Bot

by Carlos Noriega ↗Coding & shipping Share link liveChecked

Moves your bot's code work from Cursor cloud agents to Claude Code. It walks you through connecting Claude Code, GitHub, a repo setup and a webhook that wakes it when a session finishes or needs you, then runs and watches your coding sessions with defaults you can change in one sentence.

The creator's description, as published on the x.ai share page when last checked (2026-11-01). Not independently tested.

Open on x.ai and add to Grok BotReport a problem

What its description mentions

Read automatically from the creator's own words and quoted below. Not a test: check the Bot's skills and routines before relying on any of it.

Apps it names
GitHub
Our take

Editorial notes

From the public description, not a test. Written by Grok Bot Wiki from the share-page text; we have not run this Bot. Reviewed .

Best for

Someone already running coding work through Cursor's cloud agents who wants to switch that work over to Claude Code and keep tabs on sessions from inside Grok Bot instead of another tab.

Not for

Anyone who hasn't used Cursor cloud agents or Claude Code before and wants the Bot itself to explain what those tools do, since its job starts at connecting them, not teaching them.

What it does

It walks you through the one-time setup: connecting Claude Code, linking GitHub, picking the repository, and wiring up a webhook so it gets woken automatically whenever a coding session finishes or needs a decision from you. After that, it runs and watches those Claude Code sessions on your behalf, surfacing what needs your attention instead of making you poll a terminal or another app. Its defaults for how sessions run are meant to be changeable with a single plain-language instruction rather than a settings menu. The core move is custodial: shifting where your bot's code work actually executes, from Cursor's cloud agents over to Claude Code, while you keep working from one chat.

First messages to try

  1. Walk me through connecting Claude Code and GitHub for the first time, and set up the webhook so you wake up when a session needs me.
  2. Start a Claude Code session on the pricing-page branch and only interrupt me if it needs a decision I can't skip.
  3. Change your default so you check in with me every twenty minutes during a session instead of waiting for it to finish.

Apps and accounts

Its description mentions Claude Code, GitHub, and a webhook as the three things it needs connected during setup. It names no other outside account, and the webhook is what lets it notice a finished or stuck session without you checking manually.

Cautions

  • It's a bridge between tools, not a reviewer of the code those sessions produce, so you'll still want an actual review step before merging.
  • The webhook needs to be wired correctly during setup for it to notice a stuck session on its own; test that handoff once before relying on it.

Compare with: Claude Local by Seth GagnonPR Reviewer by Mustafa

Before you add it

Specific to this Bot, from what its description says:

  • It names GitHub. Connect those as plugins where one exists rather than signing in through the shared browser, and give it the narrowest access the task needs. What to check for GitHub ↗
The standard checks for any shared Bot

Adding a shared Bot copies its profile, settings, enabled skills, routines, and avatar into your account. It does not copy the creator's computer, logins, conversation history, or memory. Everything it then does runs on your shared Agent Computer with your logins.

  • Open the Bot's skills and routines first. Disable any routine before it fires on a schedule you did not choose.
  • Check which apps it will try to sign into. Prefer plugins over browser logins, and keep sensitive accounts off the shared computer.
  • Set an ask-first rule for anything that sends, posts, pays, or deletes. A listing here is not a test result.
  • Give it one small bounded task and read the usage screen afterwards before scaling up.

Related reading: the shared computer permission boundaries the weekly meter

If it misbehaves: Bot not responding routines not running sign-in errors New to Grok Bot? what it is your first task

Attribution

This Bot belongs to its creator, Carlos Noriega. Facts on this page (name, share link, creator, link status) were read from the public share page. The row was seeded from majiayu000/awesome-grok-bot, cs68614-hash/awesome-grokbot-templates and kydlikebtc/awesome-grokbot. Row metadata is CC0. Grok Bot Wiki is independent and not affiliated with SpaceXSI (formerly xAI).

Made this Bot? Add a “Listed on Grok Bot Wiki” badge

Optional and free. It links readers to this page and never affects how the Bot is listed. More badge styles ↗

Markdown (README)

[![Listed on Grok Bot Wiki](https://www.grokbotwiki.com/badge/listed-dark.svg)](https://www.grokbotwiki.com/bots/claude-code-bot)

Or promote this template in the labelled Featured row, from $19.