Guide

Where to run each Grok Bot job so you save usage

Updated · by Rosh Perera

Moving a job between Grok Bot, Cursor and Cloud Agents won't save usage on its own: on The X Subscription, eligible Grok Bot, Cursor, Cloud Agents and Grok apps draw from one weekly pool. What you can choose is where the work runs, on the Bot's cloud computer or your own Mac or PC, and how often it runs.

Owners who almost make it to weekly reset ask how to "balance usage between Grok Bot and Local," and builders ask how to optimize Cursor projects when Grok Bot drives cloud agents (user reports, 26 Oct 2026). The honest rule: on The X Subscription, eligible Grok Bot, Cursor, Cloud Agents, and Grok apps draw from **one weekly pool** (Cursor Usage and limits; Plans; xAI Usage limits). Moving a job to Cursor Cloud Agents does **not** create a free second bucket - our usage-ran-out-fast guide already says this. What you can choose is **where the work runs** (cloud Bot computer vs your Mac/PC) and **how often** it runs. This page maps those choices. We invent no per-token prices. Our free Grok Bot usage check ranks likely burners. Facts checked 27 Oct 2026. We're an independent site, not part of xAI or Cursor.

Key points

  • Default: Grok Bot cloud computer: - browser, files, connectors; keeps working when the laptop is closed (xAI computer-and-apps; FAQs).
  • Your desktop (Execution on this computer): - only when the file or command exists only on that Mac/Windows machine, or when a site drops the cloud network (xAI approvals; FAQs). Default Ask every time.
  • Route traffic through this computer: - different switch; sites see your IP (xAI settings; our route-traffic guide in this pack).
  • Cursor editor / Cloud Agents: - same shared weekly pool on The X Subscription (Usage and limits). Use them for coding workflows you already run in Cursor, not as a free offload from Bot.
  • True offload outside the pool: - work you do yourself, or on a tool billed outside The X Subscription. We do not invent a "local model" product inside Grok Bot.

Pick a place for the job

  • Email, calendar, CRM, drafts, most browser admin -> Grok Bot cloud

    Prefer Connect apps when one exists (computer-and-apps). Schedule daily or weekly, not every 15 minutes (Routines help).

  • A file that only exists on your laptop -> attach it, or Ask every time local execution

    Attach to chat when you only need the file (xAI files pattern on local-computer guide). Use Execution on this computer only for commands that must run on that machine (approvals; FAQs). Set back to Never allow when done (our local-computer guide).

  • Site blocks the Bot cloud IP -> Route traffic (desktop app open), not a plan upgrade

    Settings > Computer > Your computer > Route traffic through this computer (settings docs; FAQs). See our route-traffic guide.

  • Heavy coding / repo work -> Cursor editor on purpose, knowing it shares the week

    Cloud Agents and Agent in the editor draw from the same pool (Usage and limits). Keep coding sessions scoped; check Usage before a long run (Plans help).

  • Protect the Bot week from Chat / Imagine / noisy monitors

    Cut Grok apps first (x.ai/pricing). Switch frequent watchers to daily (upgrade-or-buy-credits edit in this pack). Pause what you do not need (Routines help).

  • Re-check the meter after you move work

    Usage at grok.com/dashboard. Our usage planner worksheet ranks Bot-side burn; it cannot invent a Cursor-vs-Bot split the products do not show.

Not sure which jobs fit your business?

Build my free AI plan →

Or get every routine pre-written in the pack →$29 one-time, plus local tax where it applies.

Get the free AI Team Starter Kit

4 copy-paste agent prompts, a business brief template and a 7-day plan, as a PDF. Plus this guide's templates.

Ready-made use cases

  1. 01CEO morning brief in 5 minutes
    One message each morning: calendar, urgent emails, money in/out, and the 3 things that move the business today.
    ~3h/week · estimate
  2. 02One daily list of drafts to approve
    Your bots hold every email, message and post they write as a draft. Once a day (or once a week) you get one numbered list and answer approve, edit or reject for each. Nothing goes out unapproved.
    ~1h/week · estimate

Example: Grok Bot setup

Grok Bot routine: CEO morning brief in 5 minutes
Schedule: Daily 7:30

Every morning, read my calendar for today, my unread emails from the last 24h and yesterday's revenue. Send me a brief: (1) meetings with one prep note each, (2) emails that need my reply with a suggested one-line answer, (3) money in/out, (4) the 3 highest-leverage tasks for today. Keep it under 200 words.

Rules: draft first, never send or post anything external without my approval. Keep summaries short.

Grok Bot, ChatGPT, Claude and n8n versions: all templates

Email me this template + the Starter Kit

What should you keep in mind?

  • "Offload to Cloud Agents" does not save included weekly usage on The X Subscription (Usage and limits; usage-ran-out-fast).
  • We publish no $/token or "local model saves X%" figures.
  • Always allow on the first local prompt applies to every Bot (approvals). Prefer Ask every time.
  • Linux / phone: Route traffic and local execution follow desktop settings docs - phone alone is not the documented path for local routing (user reports; settings: Your computer on desktop).

Get the free AI Team Starter Kit

4 copy-paste agent prompts, a business brief template and a 7-day plan, as a PDF. Plus this guide's templates.

Free gets you 4 starters. Pack adds the CEO that assigns the rest · $29

Day 0 on the pack is a CEO agent plus one worker and a morning brief in about 15 minutes, drafts only. Free kit stays free; the pack is the CEO hand-off, role pack and weekly scorecard when you want the rest assigned.

Get the pack · $29 →See what's inside

$29 one-time, plus local tax where it applies.

14-day money-back guarantee: reply to your receipt within 14 days for a full refund.

Built by Rosh Perera, who runs a team of bots for his own businesses.

FAQ

How do I balance Grok Bot and Local so I last until reset?

Keep most jobs on the cloud computer with wider schedules. Use local execution only for desktop-only files/commands. Cutting Chat/Imagine and hourly monitors usually saves more than moving jobs between cloud and local (Routines help; pricing pool).

Does running a Cursor project from Grok Bot use extra usage?

Coding and Cloud Agents draw from the same weekly pool as Grok Bot on The X Subscription (Usage and limits). Scope the project work and check Usage before long runs. No separate free project bucket.

Will a local model on my PC use Grok Bot usage?

Grok Bot does not document a built-in "run on my local LLM instead" switch that zeros Bot usage. Local execution means commands on your desktop under your approval policy (approvals), not a second AI plan we invent.

Get a plan for your exact business

Build your free AI team. No signup.

Build my free AI plan →Or take the free quiz: which AI agent fits your business →

Related guides