← Back to catalog

Grok Bot’s usage cut has a lot of people frustrated, including me. I’m dropping to the base tier, and here’s how I’m moving my bot operations over to Claude without starting from scratch:

Ask each Grok Bot to write down its purpose and tasks, recreate those as Claude projects or scheduled tasks, and keep anything that changes or buys behind your approval.

For

Usage cuts make Grok Bot too tight and you want the same jobs elsewhere without a full rewrite.

When you're done

Same jobs on Claude projects/schedules; buy/change actions still need your OK.

How

  1. 01

    Ask each Grok Bot to write down its purpose and tasks.

  2. 02

    Take that write-up to Claude and recreate each as a project with standing instructions or a scheduled task.

  3. 03

    Keep anything that changes state or buys something behind your approval.

  4. 04

    Run both in parallel briefly and note what breaks before you drop the Grok side.

Notes

What's good: export purpose+tasks first so you don't rebuild from memory. The catch: connectors and calling may not map 1:1; expect breakage and retest.

Related plays

Write-ups follow public posts and official docs. No likes, views, or dashboard numbers. Open the source to check the original. About