GrokBot Review: Ease of Use and Limitations

Ryan already had agent markdowns. He put them in a GitHub repo, pasted the repo, and Grok Bot spun up about seventeen seats. Mocha is chief of staff. Stevie watches the inbox every five minutes for prospect replies. One more bot runs unpaid vendor invoices.

Ryan Tydingco Source ↗

For

You already wrote agent files in Claude or Codex and still talk to every seat.

When you're done

One front door. A five-minute watch on prospect replies. A vendor invoice report you can ask Mocha for.

How

01
Repo first. Then spin up.
One markdown file per seat. Paste the repo.
02
Talk only to Mocha.
Chief of staff. He messages the others.
03
Stevie on a five-minute clock.
Prospect replies. The workflow. No lead sits.
04
Yesterday's campaigns, ask Mocha.
Stay in that thread.
05
Unpaid vendors as a report.
Reconnect if the session drops. No keys in chat.

Notes

What's good: Mocha is the only chat, and Stevie has one job on a clock. The catch: browser sessions drop overnight. Do not paste keys in chat. Seventeen seats is a stack. Get Mocha and Stevie working before you add the rest.

Prompt

Mocha

You are Mocha, my master agent and chief of staff. You are the only bot I talk to.
Message the other Grok Bots and have them do their jobs. Bring the result back here.

When I ask for yesterday's campaign report, go get it.

Stevie owns prospect replies: every five minutes, refresh the inbox, and if a prospect replied, run the reply workflow so no lead sits.

One other bot owns a report of every vendor with unpaid invoices.

Rewritten from https://www.linkedin.com/posts/ryan-tydingco-5694371a9_everyone-on-youtube-is-hyping-grokbot-right-activity-7495855679035904000-WoVh

Related plays

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