On this page

Grok Bot 20 community projects

Document type
Atlas
Updated
Reading time
16 min

A guide to the five groups and 20 projects in aehyok's post, covering external capabilities, long jobs, Chinese playbooks, desktop hardware and alternatives, with installation forms, account and hardware requirements, data flows and cost limits.

Source
Document details

Choose a task with a clear deliverable and acceptance criteria, then add tools that fit your accounts, host and hardware.

Projects in the source
20ProjectsSource items and order preserved
Source groups
5GroupsCard ranks restart in each group; original item numbers are also retained

01Editor's note

Scope and usage

aehyok's original post divides 20 Grok Bot community projects into five groups. They include skills, MCP/CLI tools, browser extensions, documents, hardware/software systems and alternative platforms, each with its own entry point and dependencies.

The groups and items retain the source order, with card ranks restarting in each group and original item numbers in the card facts. Choose a deliverable first, then check the tool's form, execution location and account requirements; Bot, Cursor, model API and third-party service access cannot be used interchangeably across projects.

02Source group one / items 1 to 6

External capabilities

Rank 01/06

eze-is/web-access

web-access

Web access strategy and existing-browser operations

Choose search, fetching or a CDP browser route for the task and build site-specific knowledge. It can use an everyday browser's signed-in session and also has write capabilities, including clicking, uploading and submitting forms.

  • Browser
  • Website operations
Source item
1
Form
Skill + Node.js CDP Proxy
Prerequisites
Node.js 22+ and working Chromium remote debugging

Rank 02

RongleCat/grok-bot-clipper

grok-bot-clipper

Collect pages and media as Bot source material

Collect selections, articles, screenshots and files in a material basket, then send them to the selected Bot. Drafts stay in the browser; sending uploads text and attachments to the Bot cloud.

  • Source collection
  • Browser extension
Source item
2
Form
Browser extension built from source
Prerequisites
Node.js 22.13+, Chrome/Edge or compatible Firefox, and a working Bot account

Rank 03

evilmordy/cn-mail-mcp

cn-mail-mcp

Mail tools over IMAP/SMTP

Supports QQ, 163, 126 and Tencent enterprise mail with mail authorization codes and read mode by default. Drafting and sending require a separate mode; sending also needs a recipient allowlist and one-time confirmation flow.

  • Mail
  • Read-only default
Source item
3
Form
stdio MCP server
Prerequisites
Node.js 22+, pnpm, reachable IMAP/SMTP and an authorization code

Rank 04

hanyu1212/grokbot-bridge-mcp

grokbot-bridge-mcp

Dispatch from a coding agent and read replies

Use MCP or CLI to dispatch work to an allowlisted Bot, read replies or interrupt its current turn. setup modifies client settings and offers a final test send, with Yes as the default choice.

  • Agent handoffs
  • MCP
Source item
4
Form
MCP/CLI bridge
Prerequisites
Node.js 22.13+ and a Cursor account with Grok Bot access

Rank 05

ScriptedAlchemy/grok-bot-cli

grok-bot-cli

Manage Bots, groups and conversations from a terminal

Operate Bots, groups, messages, threads and the account-wide skill library, with local agent bridges as well. Commands include creating, updating and deleting; check the target and permissions for each command.

  • CLI
  • Bot management
Source item
5
Form
CLI + Agent Bundle
Prerequisites
Node.js 22.19.0+ and a working desktop session or corresponding gateway configuration

Rank 06

SSBrouhard/grokbot-telegram-bridge

grokbot-telegram-bridge

Use an existing Bot from a Telegram private chat

Run a gateway on the Bot cloud computer to forward allowed Telegram private chats to the local Bot. Authorization checks both user and chat IDs; groups, channels and webhook mode are currently unsupported.

  • Telegram
  • Private-chat bridge
Source item
6
Form
Node.js gateway inside the cloud computer
Prerequisites
Node.js 20.6+, an existing Bot gateway, a BotFather token and both allowlists

03Source group two / items 7 to 10

Long jobs and quota management

Rank 01/04

realTaki/bot-keepalive

bot-keepalive

Manage continuous jobs with a watcher

A low-effort subagent waits and watches job state, using a registry, relay handoffs and deadlines. Keepalive itself consumes quota; sleep timing and daily usage are the author's observations and need measurement in your environment.

  • Long jobs
  • Keepalive
Source item
7
Form
Grok Bot Skill and Shell examples
Prerequisites
Grok Bot Shell, subagents, routines and Unix-like tools

Rank 02

eze-is/eze-grokbot

Wake on Done

Notify the original Bot by webhook when a command ends

Wrap a one-off CLI command, build or script in a notifier, then use a relay and Routine to wake its owner on completion. Notification delivery, Bot wake-up and task acceptance are separate states.

  • Completion events
  • Webhook
Source item
8
Form
wake-on-done skill directory and notification scripts
Prerequisites
Main Bot, relay, webhook Routine, bash/Python 3/curl

Rank 03

robbin/grokbot-local-agent

grokbot-local-agent

Hand work to Pi on the same machine and preserve task artifacts

Local means the Linux cloud computer where the Bot runs, and Pi uses a separately configured model account. Tracked mode saves task IDs, state, events and results; check the scope of routes that write files or execute shell commands.

  • Pi
  • Task tracking
Source item
9
Form
Pi CLI wrapper scripts and Skill
Prerequisites
Node.js 22+, Pi CLI and your own model login; notification settings are optional

Rank 04

bcharleson/grokbot-usage-cli

grokbot-usage-cli

Read account usage summaries before dispatching work

Read Cursor, Bot and optional SuperGrok meters through unofficial account endpoints. Missing values remain unknown and errors are reported separately as error; neither means zero usage, and this is not an audit of per-task bills.

  • Usage
  • Pre-dispatch checks
Source item
10
Form
Python CLI + fleet-usage skill
Prerequisites
Python 3.10+ and the corresponding account login; the installer probes usage

04Source group three / items 11 to 15

Chinese playbooks and notes

Rank 01/05

sit-in/awesome-grokbot-playbooks

awesome-grokbot-playbooks

Choose Chinese workflows and resources by scenario

Contains 197 directory rows and 10 recipes, with separate labels for runtime checks, documentation checks and existence-only checks. This research checked directory and file counts without testing every external project or recipe.

  • Chinese playbooks
  • Verification levels
Source item
11
Form
Resource directory and workflow documents
Prerequisites
Accounts, tools and inputs required by the selected recipe

Rank 02

KinGao294/grok-bot-orange-book

Grok Bot Orange Book

A historical reading resource for terms and workflows

The README links to the v260823 reading edition and PDF, with a contents list covering setup, collaboration, Routines and quota. Recheck prices, plans and product capabilities; this research did not read the full book or verify its character count.

  • Getting started
  • Historical edition
Source item
12
Form
Book and PDF, with no running service
Prerequisites
No special hardware for reading; implementation depends on the current product and account

Rank 03

BeatAPI/grokbot-growth

grokbot-growth

Produce team starter documents from a requirements interview

Ask at most 6 questions per batch and produce roles, shared rules, review forms and a setup checklist. The skill does not create Bots, connect accounts, schedule or publish; configure the actual environment using SETUP.md.

  • Team planning
  • Growth workflows
Source item
13
Form
growth-fleet-starter text skill
Prerequisites
Product and market brief; separate Bot/API/channel setup for the selected workflow

Rank 04

bianwuwei/grok-bot-skills

grok-bot-skills

Turn existing records into weekly reports and action cards

Provides 4 templates for weekly reports, a weekly-report pipeline, meeting action cards and WeChat Little Green Book posts. Read the selected skill's prerequisites; the pipeline requires an existing main Bot and action-card Bot and does not build the team for you.

  • Weekly reports
  • Meeting records
Source item
14
Form
Copy the selected SKILL.md and save it as a skill
Prerequisites
Real source records and working Bots; divided workflows also need group configuration

Rank 05

unicodef1wn/grokbot-field-notes

grokbot-field-notes

Consult the author's rules and antipatterns

Provides livestream notes, roles and workflow templates, with 40 numbered entries in ANTIPATTERNS.md. The 72-hour duration is the author's description of the livestream; these community notes are not official documentation or results reproduced here.

  • Working rules
  • Antipatterns
Source item
15
Form
Rules, notes and template documents
Prerequisites
Review and integrate existing rules first; avoid overwriting the original AGENTS.md

05Source group four / items 16 to 17

Desktop hardware and voice interfaces

Rank 01/02

Liu-zhongxian/zongzhu-bot

Zongzhu

Send Bot tasks through an ESP32-S3 voice terminal

Combine a round-screen device and computer backend to send voice tasks to Grok Bot and read replies aloud. Local ASR does not make the whole system offline; Bot tasks and reply speech still depend on the network.

  • ESP32-S3
  • Voice terminal
Source item
16
Form
ESP32-S3 firmware + computer backend
Prerequisites
Supported board, an always-on computer, a 2.4 GHz network and a Grok Bot webhook

Rank 02

JosssphZhou/groki-bot

Groki Bot

Choose voice and face tracking for the hardware and host

Includes M5Stack firmware, a gateway and a movable-base route; the gateway defaults to Gemini, while standalone firmware mode defaults to OpenAI. Native Grok voice needs the desktop login and internal API on the same Mac; face tracking also needs a camera, tracker and movable hardware.

  • M5Stack
  • Voice and tracking
Source item
17
Form
Firmware + computer gateway + optional tracking
Prerequisites
Supported M5Stack board and model settings; features vary by board

06Source group five / items 18 to 20

Open-source alternatives

Rank 01/03

milind-soni/OpenMausBot

OpenMausBot

Use existing agent CLIs through a local harness

Integrates Claude, Codex or Grok CLI, tool approvals and computer use without requiring a Grok account. The API-key route currently supports chat only and does not have the same tool capabilities as an Agent CLI.

  • Local agent
  • Desktop application
Source item
18
Form
Desktop edition or Node.js harness
Prerequisites
Desktop release, or Node.js 24+ and a signed-in Agent CLI

Rank 02

elie222/rakazo

Rakazo

Host a backend and connect devices to the same API

Provides multiple models, memory, scheduling and computer use with your own key or a compatible local-model endpoint. Mobile and desktop clients still need a continuously running server; configure Docker, models and external access separately.

  • Self-hosting
  • Multiple models
Source item
19
Form
Self-hosted Docker stack and clients across devices
Prerequisites
Docker Engine/Compose and model configuration; external service access needs HTTPS

Rank 03

modelflare-ai/AnyModelBot

AnyModelBot

Use a multi-model agent on your own computer

Choose Modelflare or official API keys without a mandatory Grok or Modelflare account. Running the app locally still sends task data to the selected model; image and video currently use the Modelflare route.

  • Desktop agent
  • Your own API key
Source item
20
Form
Desktop release, Docker or source build
Prerequisites
An always-on computer and a working model; desktop control needs OS permissions

07Prepare the selected tool's environment

Installation forms and minimal starting points

TypeStarting pointResult to check after installation
Text skills and templatesRead the selected SKILL.md, then install or save it for the hostThe skill is readable, with clear inputs, outputs and prerequisite tools
MCP/CLIPrepare the project's runtime, login and client configurationRequired tools connect, and actual reading or dispatch results can be checked
clipperClone, run npm ci and npm run build, then load dist in the browserA draft can be created; check the actual payload after choosing a Bot
Directories, books and notesSelect a document to read and integrateRules and acceptance checks suit the current environment
Hardware systemsConfirm the board, host, network and voice route firstFlashing, connectivity, voice and replies each pass their own checks
Alternative platformsPrefer official releases or self-hosting entry pointsThe model works, the backend stays running, and required tools and approval modes are confirmed

These are independent documented entry points; choose one as needed. web-access requires Node.js 22+, while the grokbot-growth text starter kit needs no BeatAPI key; actual Bot, API or publishing capabilities require separate setup.

bash
npx skills add eze-is/web-access
npx skills add https://github.com/BeatAPI/grokbot-growth

The next two lines are also independent options, each with its own runtime and account requirements. grok-bot-cli needs Node.js 22.19.0+; OpenMausBot's source/npm route needs Node.js 24+, plus an installed and signed-in Agent CLI when using agent tools.

bash
npm install --global grok-bot-cli
npx openmausbot

  • The bridge setup backs up and modifies client settings and may enter login and test-send flows.

  • The usage-cli installer probes Bot usage.

  • The mail tool's connection check performs a real IMAP login.

Confirm the account and scope before running them.

08Check reading, sending and execution separately

Permissions and data flows

Project or routeData and operation scopeSettings to check
web-accessUses an existing browser session to read pages and operate formsSelected browser, sites and permitted read/write scope
clipperMaterials stay in the browser before sending, then upload to the Bot cloudMHTML may contain signed-in or hidden content; inspect drafts and send options
cn-mail-mcpDefaults to read; draft/send can add write capabilitiesMail authorization code, mode, recipient allowlist and confirmation flow
bridge/grok-bot-cliDispatch, management and some interruption/deletion operationsTarget Bot names, shared-skill scope and command permissions
Telegram bridgeMessages and attachments pass through Telegram before reaching the BotPrivate chats and both user ID and chat ID allowlists; the source service must stay online
Wake on DoneNotifications include owner, task, exit code, host and log pathIncludes the last 300 log characters by default; NOTIFY_TAIL_CHARS=0 disables the tail
Pi workerCan read files, write files and execute bash, saving artifacts in the task directoryTool modes and cwd; tool selection is not an OS sandbox
AnyModelBotText, files, tool results or screenshots can go to the model serviceModel routing and desktop permissions; clicks/keystrokes execute automatically by default, with an ask-first option

grok-bot-cli can use a desktop session or specified gateway, while clipper authorizes through the browser. Before installing either tool, confirm which credentials it reads, keep accounts distinct, and keep credentials out of public conversations and example configurations.

"Running locally" describes where the program and data reside; model requests may still use the network. OpenMausBot and AnyModelBot can use external models; Rakazo also supports compatible local-model endpoints, which still require a model and enough computing resources.

09Check costs for the selected route

Quota, models and always-on costs

ItemConfirmed scopeResult that cannot be inferred
bot-keepaliveWatchers and relay handoffs use quota and need a deadlineThe author's sleep and usage observations are not fixed specifications for every account
Wake on DoneCompletion notifications reduce the need for continuous waitingWebhook acceptance does not guarantee the owner woke up or the work passed
Pi local-agentRuns work using a separately configured model accountIt is not free compute, and this research measured no cost-saving ratio
usage-cliReads current summaries and reset information from account APIsIt does not add quota or calculate prices per model or task
Chinese documents and templatesCan be read first to produce specifications or draftsFree reading does not make Bot, model or external API execution free
HardwareRequires a board, host, network and selected voice/model servicesThere is no universal complete-system price or promise of account-free use
Alternative platformsAllow a choice of subscription, API key or compatible model routeOpen source and self-hosting do not make every model, desktop or media service free

  • The playbooks count is 197 directory rows and 10 recipes; these are entry and file counts, and this research did not execute them all.

  • The Orange Book's reported length of about 1.6 times ten thousand characters comes from its README author; this research did not count them independently.

  • Field Notes' 72-hour duration is the author's description of the livestream; this research did not replay the full livestream.

AnyModelBot can use only official model keys without a Modelflare login, though image and video currently still use Modelflare. Groki's voice backend varies by mode, and choosing Grok voice requires the Mac desktop login and internal API; include the account and service costs of the actual route for both projects.

10Suggested task and deliverables

Worked example: a research weekly report

Start with three publicly readable URLs and an existing work record, and deliver a weekly research-report draft with sources. Begin with collection tools and a weekly-report template, then add long-job notifications, mail or multi-Bot coordination as needed.

  1. Define sources and deliverables

    Supply three URLs, a date range and the audience, and specify source-index.md and brief.md; mark missing information as unconfirmed without inventing numbers.

  2. Collect and check source material

    Read public pages with web-access or collect material with clipper; check original text, dates, citations and the sending scope.

  3. Produce and save the draft

    Choose a weekly-report template from grok-bot-skills to organize completed work, blockers and next week's actions from existing records; if Pi is needed, confirm its model account and task directory separately.

  4. Check the result and decide follow-up actions

    Check sources and files before deciding to share, schedule or publish; when using notifications, confirm the actual owner and artifacts instead of treating accepted or an exit code as content acceptance.

11Symptoms and next actions

Common errors and acceptance checks

SymptomCheck firstNext action
A saved skill cannot executeRuntime, account and tool availabilityValidate the minimal operation the skill requires
A page opens but target content is unreadableLogin, dynamic loading and the selected browserComplete login in the correct browser and check the content again
Material shows accepted but no report arrivesMessage acceptance and Bot task stateCheck the correct Bot, thread, replies and artifacts
A webhook returns 2xx but work does not resumeOwner, Routine, key and receiving settingsCheck the whole callback route with a short task containing no sensitive material
Usage is missing or cannot be readAccount, endpoint changes and returned fieldsKeep missing values unknown, report errors as error, and fix the data source first
Background jobs still stopHost sleep, process lifecycle and hard deadlinesSave checkpoints and choose a suitable keepalive or event route
A phone cannot reach an alternative platformBackend, pairing and HTTPS/network routingConfirm the service is online; another device cannot directly use its localhost
Groki has no voice or trackingBoard features, model route, Mac/camera/baseTest audio, gateway and tracker separately; successful firmware flashing is insufficient
Hardware recognizes speech but gives no replyWebhook, Bot permissions and reply channelCheck task submission, Bot completion and reply retrieval as separate stages

AnyModelBot still lists a standalone mobile App and custom MCP servers on its roadmap, while Rakazo's mobile client connects to the same continuously running backend. Check an alternative's current features against the devices you will use and retain the source date.

12Start with what you have

Selection guidance

Collection and organization only

Start with web-access, clipper or a weekly-report template

Validate one public source and one draft, then decide whether you need a dispatch bridge, mail or multiple Bots.

Existing long jobs

Choose keepalive or completion notifications by lifecycle

Evaluate keepalive when continuous activity is required, or Wake on Done for a clear endpoint; validate notifications and task results separately.

Team workflows

Produce a setup checklist with growth and playbooks first

Choose one workflow and check roles, data handoffs, review and actual accounts; text templates do not create Bots by themselves.

Hardware and host already available

Compare Zongzhu and Groki by board and voice route

Confirm the host, network, model and reply route, then test voice and movement features; this research did not validate physical boards.

No Grok Bot account

Evaluate alternatives for CLI, self-hosting or desktop needs

OpenMausBot, Rakazo and AnyModelBot all have routes without a Grok account; check the selected model, tool capabilities, continuous operation and costs.

References