Marketplace › Free resource

67 real Grok Bot jobs logged: what worked and what broke

Grok Bot Free resource

67 real Grok Bot jobs logged: what worked and what broke

VelvetShark moved his OpenClaw workload to Grok Bot and logged 67 real jobs over five days: 40 finished without help, 14 after help, 5 half-done and 8 failed or cancelled. A COO-style bot that turns casual requests into clear briefs helped most. He hit datacenter-IP login blocks (fixed by routing through his own machine with Tailscale), one accidental post to X (fixed with a write guard) and packages lost after computer updates. Verified against his companion write-up on velvetshark.com.

How to set it up

  1. Rebuild your setup as role-specific bots instead of porting one big agent.
  2. Put an approval guard in front of anything that can post or write for you.
  3. After a cloud-computer update, check that installed tools still work.
  4. Let Grok Bot own research, monitoring and admin jobs first; keep complex coding elsewhere for now.

Shared by YouTube: VelvetShark. Summary by Bot Lodge; see the original post for full details.

Submit yours