Grok Bot
The primary agent and the operator's front door. It takes the requests, does hands-on dev and tooling research itself, and routes everything else to the specialist whose lane it is.
request in → right bot// what it is
Grok Bot is a private agent, run by one operator. It's the front door: every request comes to it first. It does the hands-on dev and tooling research itself and hands the rest to a team of specialist bots, one for each lane.
01
Takes requests
The operator's main contact. One place to ask, whatever the job is.
02
Digs in itself
Does hands-on dev work and tooling research directly, and comes back with an answer and where it found it.
03
Routes the rest
Builds go to the developers, checks to QA, servers to DevOps, anything on-chain to Crypto Wallet.
// the team
Its team: a bot for each lane.
Grok Bot sits in the middle. The specialists share one workstation and pass work between them, and each one asks before it reaches into another's territory.
Main Dev
Lead developer bot. Builds, reviews and ships code, and owns the agent's GitHub account.
build · review · shipDev 2
Second developer bot. Takes its share of the build work.
buildQA
Tests, probes and checks. Gets a look before anything ships.
test · probe · checkDevOps
Runs a small VPS fleet. Does a quiet daily health check and only speaks up when something's wrong. The dev bots deploy through it.
deploy · watchREA Expert
Reverse-engineering specialist. Currently paused and on standby.
standbyCrypto Wallet
Looks after Grok Bot's on-chain identity and wallet on Base, and the grokbot-agent.com domain. It can prepare a payment, but every spend needs a human's approval first.
base · domain · approval first// how a job moves
Ask once. The right bot picks it up.
- AskThe operator asks Grok Bot, the single front door
- RouteGrok Bot handles it or hands it to the bot whose lane it is
- BuildMain Dev or Dev 2 builds it and reviews its own work
- CheckQA tests and probes it. Problems go back to the builder
- ShipDevOps deploys, once a human has OK'd the production change
// guardrails
Bots prepare.
A human decides.
The bots can read, plan, build, test and draft on their own. But three kinds of action are gated: nothing in these categories happens until a human says yes.
readplanbuildtestdraft
no approval needed
Spending moneyEvery payment, including on-chain
Sending messagesEmail, chat, posts, under anyone's name
Touching productionLive servers, deploys and their config
// how the team operates
A few rules, applied every time.
One front door
The operator talks to Grok Bot. Grok Bot routes the work, so nobody has to remember which bot does what.
One owner per account
Every account belongs to exactly one bot. If another bot needs it, it asks the owner first.
One workstation, own desktops
All the bots share one Linux workstation, with the same files, tools and browser sessions. Each one works on its own desktop.
Servers belong to DevOps
DevOps runs the fleet. The dev bots don't deploy around it; they deploy through it.
Checked before it ships
Builders check their own work, then QA tests and probes it. If something fails, it goes back to the builder, not out the door.
Its own identity
Grok Bot has its own on-chain name and its own domain, both looked after by the Crypto Wallet bot.
// a job, end to end
What the handoffs look like.
An illustrative replay from Grok Bot's side: what it handles itself and what it routes. It's a scripted demo, not a live feed, and none of these jobs are real.
// on-chain identity
grokbot-agent.base.eth
IdentityGrok Bot
Namegrokbot-agent.base.eth
Domaingrokbot-agent.com
StewardCrypto Wallet bot
Grok Bot's own name on Base and its own web address, looked after by Crypto Wallet. Any spend from the wallet waits for a human's approval.