Save Grok Bot usage: Python + Cursor under the seats

Qué instalar o crear

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.

El prompt

Esto es un consejo, no un prompt de sistema para pegar. El autor no publicó uno. Sigue los pasos del primer uso.

Primer uso

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.

Qué ajustar

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

Fuente

Herbie Clarke @echrisclarke · Publicación original

Sin afiliación con xAI. No escribimos este prompt. Siguen aplicando las condiciones de las plantillas de terceros.