Grokbot TemplatesGrokbot Templates
All use cases

Engineering

Save Grok Bot usage: Python + Cursor under the seats

Seats burn weekly usage on GETs, merges, and long research.

Share

What hurt

Herbie Clarke hit Grok Bot usage limits running real work. He kept specialist seats for supervision, votes, and final calls, but moved model-heavy jobs into Cursor and no-model jobs into Python + Windows Task Scheduler. Hide is not pause — a hidden seat can still burn a live routine.

What to install or create

Dump every profile/automation to disk first. Local parent runner writes data/<job>-latest.md; weekday packs on Task Scheduler (or cron). Shared cursor-jobs JSON (GET/PATCH merge-by-id) lets seats hand work to local Cursor CLI (no Cloud Agent, no --yolo on his desk). Optional Cursor Automations webhook for unattended wakes. Cursor may consult seats via the desktop app; irreversible steps stay on your approval rail. Read his Article on the source post.

Bots

  • Face seat

    Briefs from finished local files; supervises; routes votes. Does not collect weekday packs itself.

Plugins

  • Browser

    Optional

Files

  • data/<job>-latest.md outputs; shared cursor-jobs JSON on a hub you control.

Routines

  • Local weekday packs (e.g. 06:30 money, 07:10 runner). Pause matching Grok Bot routines only after local runs succeed on schedule.

The prompt

This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.

First run

  1. 1Read https://x.com/echrisclarke/status/2096399969297010933 and the linked Article “How I save Grok Bot usage by moving heavy work into Cursor”.
  2. 2Export every Grok Bot profile and automation (schedule, trigger, owner, purpose). Note: Hide ≠ pause.
  3. 3Move no-model jobs (GET health checks, pulls, digests) to a local Python runner that writes data/<job>-latest.md on Task Scheduler or cron. Keep the old routine until the replacement fires for real.
  4. 4Add a shared cursor-jobs list (API, gist, or repo file) with merge-by-id. Seats enqueue heavy jobs; local Cursor CLI drains them.
  5. 5Keep send/trash/pay/submit on your approval fence. Let seats brief from finished files instead of re-collecting.

Approval fence

Do not send, trash, pay, submit, unlock, or overwrite live data without your yes. Mail cleanup stays candidate-list until an approval item exists.

What to tweak

Seats supervise; scripts collect; Cursor thinks long. Pause/delete old Grok Bot clocks after the local schedule is boring. Never treat Hide as stop.

Source

Herbie Clarke @echrisclarke · Original post

Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.

Browse templates

Browse team blueprints