Marketplace › Free resource

Grok Bot Free resource

Why one builder stopped using Grok Bot after a 78-PR week

Alice Moore ran 16 bots that helped her land 78 pull requests in a week, then watched them burn about $100 over one weekend, mostly on wake-ups where a bot decided it had nothing to say. She credits the cloud-plus-your-computers design, password-free sign-ins and speed, but documents dropped follow-ups, late routines and a $200 plan she still outgrew. Her fix list: let plain code handle routing and follow-ups, and models only the thinking. She works at Builder.io, which makes a competing open-source framework, and says so.

1. Set an on-demand spend limit before leaving routines and webhooks running overnight.
2. Filter events in plain code so only the ones worth acting on wake a bot.
3. Don't trust "I'll get back to you": keep follow-ups in a task board or document you can see.
4. Prefer event triggers over frequent schedules, and keep busy bots to narrow jobs.

Submit yours