What the source did
- He runs 9 teams and 34 bots (33 on teams plus Mika, his main bot).
- The campus shows who's working, approvals pending, a usage battery by team and by bot, and scheduled tasks. He can approve from the page without opening chats.
- Mika built it over rounds: first flat, then 3D. It lives on a private Vercel link, with a webhook for the buttons.
- He published a GitHub repo whose skill/SKILL.md his main bot reads to build your campus, plus a public demo on Vercel.
- His article walks through: give the main bot the repo link; approve the Vercel connection; approve routine cards; paste the webhook URL and key on the private /setup page; optionally schedule refreshes.
- Safety from the README: the bot reads team chats read-only; it never creates, changes or deletes bots; the JSON has no full chats; the link is private; buttons are signed; sensitive actions confirm in chat first.
- Same-day Reddit mirror by u/Crypto_Billionaire linked the same demo and repo in a first comment.
- Engagement when we checked the X post: about 15 likes, 3 reposts, 4 replies, 11 bookmarks and about 55k impressions.
- Heads-up: this is not Alex Finn's Mission Control page prompt. That one is a Grok Bot Page; this one is a Vercel 3D campus with usage battery and webhook approvals.
“My Grok Bot teams have their own 3D campus.”— Sar (@Sar_Barshem), X
Summary written by Agent Cookbook from the original post. See the original for the full context. How we source recipes
Our notes
- What it takes
- Several Grok Bot teams already running, your main bot to read his repo skill, a Vercel account and the webhook URL+key on /setup. Demo and repo linked.
- Where it breaks
- Demo data is invented. The campus never creates or deletes bots. You need an existing multi-team setup; sensitive actions still confirm in chat. Distinct from Alex Finn's Mission Control page.
- Human checkpoint
- You approve the Vercel connection, routine cards and webhook setup. Page buttons are signed; money and send actions stay in chat.
- Tools involved
- Grok Bot with several teams already running, Your main bot (his is Mika) to read the repo skill and build the campus, A Vercel account for the private link, Webhook URL and key pasted on the private /setup page
✓ Verified Source link checked and still live. Notes by Thomas, editor. How we verify
Get their template
Made and published by Sar. Start here; it is their original, not ours.
Repo · by SarSar's grok-bot-3d-campus repo (SKILL.md)Give your main Grok Bot the repo link; it reads skill/SKILL.md and builds your campus. Demo uses invented data and sends nothing.Open it ↗Example · by SarLive demo of the 3D campusDemo data is invented. Use it to see the layout before you point your main bot at the repo.Open ↗Guide · by SarHis X article: how to give yours oneTitle: My Grok Bot teams have their own 3D campus. Here's how to give yours one. Walks through the bot steps and /setup webhook.Open ↗
Approval rule
🛡
Sensitive actions still confirm in chat first. The campus buttons are signed; the link is private; the bot reads team chats read-only and never creates, changes or deletes bots. Sending, buying, posting, and deleting always need a human.
Set it up
- Confirm you already run multiple Grok Bot teams. The campus is a view over them, not a starter setup.
- Give your main bot the repo link (https://github.com/sarbarshem/grok-bot-3d-campus) so it can read skill/SKILL.md.
- Approve the Vercel connection when the bot asks.
- Approve the routine cards it proposes.
- On the private /setup page, paste the webhook URL and key.
- Optional: schedule refreshes the way his article describes.
- Use the demo (https://grok-bot-3d-campus-demo.vercel.app) only to learn the layout — its data is invented and it sends nothing.
Common failures
⚠
- Expecting it to create or reorganize your bots. The README says it never creates, changes or deletes bots.
- Putting a public link on the campus. His is private; buttons are signed.
- Approving a sensitive action only on the page. Sensitive actions still confirm in chat first.
- Starting from zero teams. You need an existing multi-team setup for the campus to show anything real.
- Treating the demo numbers as his real usage. The demo invents its data.
Variations
- Mission Control first: if you only need a flat "waiting on me" page, see Alex Finn's Mission Control prompt.
- Approvals-only: use the page buttons for routine approvals and keep money or send actions in chat.
- Usage watch: the battery by team and bot is the main difference from a simple activity board.
Related setups: A Mission Control page for all your Grok Bots → · Grok Bot agents run from GitHub job packs → · Shared memory for an agent fleet → · Done-when lists and a two-try stop rule → · Two dozen Grok Bots run an HVAC firm's office → · Grok Bot admin team for a one-person print shop → · $320K October via a Grok Bot office team →
Get the 10 best agent setups. Free.
Plus new recipes every week. One email, no spam.
Unsubscribe anytime. Privacy