
18 / building AI agents / dms open making agents smarter, faster & cheaper Grok bots + decision models / @Roobet
Joined March 2010
- Tweets17.8K
- Following633
- Followers3.7K
- Likes36.1K
holy sh*t. Karpathy's LLM wiki idea, rebuilt as three Grok Bots that never overwrite what you told them
stop re-explaining your life to AI every chat. drop your files once and let the wiki build itself
three bots, one brain:
the reader takes every PDF, link and note you drop and locks the original. raw/ is read-only, forever
the librarian compiles it into wiki/ pages and keeps a link back to the exact source
the checker audits everything and hunts for two sources that disagree
watch what happens with one launch date:
→ source_01.pdf says "launch planned for Friday". locked
→ the librarian writes project.md: Friday, linked to source_01
→ you ask "when do we launch?". the answer gets filed back as a page, so the brain grows every time you use it
→ source_02.pdf drops: "launch moved to Monday"
→ a normal AI quietly overwrites Friday and sounds just as confident
→ the checker flags it: CONFLICT FOUND
→ both versions stay. Friday ← source_01, Monday ← source_02
→ the page now says: "Friday or Monday? ask the user"
a second brain that sounds sure while remembering the wrong date is worse than no brain
Reader collects. Librarian connects. Checker questions.
every page has to show:
> the claim
> the source it came from
> what disagrees with it
paste this into Grok Bot:
"Build me a second brain with three bots. Reader saves every file I send into raw/ and never edits it. Librarian compiles wiki/ pages with a link to the source for every claim, and files my good questions back as answer pages. Checker audits the wiki for contradictions. When two sources disagree, keep both and ask me. Never overwrite silently. Show me the structure first and do nothing until I confirm"
start with one project, not your whole life
bookmark this @karpathy
your AI inbox bot is about to promise something you never agreed to
a client DMs: "could we launch Friday? budget still pending."
a normal AI reply bot answers in 2 seconds:
"Friday is confirmed. we are ready to launch."
sounds great. except the budget was never approved
so i built a Grok inbox crew where one message goes through six bots:
> Inbox scout catches the message
> Intent sorter finds what they want: launch request, date Friday, budget pending
> Context finder pulls the missing detail: Friday is only proposed
> Reply writer drafts the answer, a little too confident
> Fact checker blocks it: "unsupported promise"
> Approval gate holds the fixed draft for you
final draft: "Friday works if the budget is approved."
status: not sent. your call.
My read: everyone's racing to make AI reply faster. the real feature is the bot that catches the reply you'd regret sending
HOLY SH*T, I SENT SIX BOTS TO FIX A DEAD NETWORK AND THEY WOKE UP A GIANT MECHANICAL SPIDER.
it’s called GROK BLACKOUT. i made an animation where you follow a repair crew through a machine without knowing what the machine actually is.
everything starts offline. connections fail, the diagnostics go quiet, and one golden scout is still moving through the wreckage.
then the repair bots arrive.
each has a separate job: ROUTE, MEMORY, POWER, SYNC, LOGIC and HEART. they carry replacement modules into position, reconnect the broken paths and send signals back toward the core.
watch the six panels at the bottom. every subsystem coming back online corresponds to something changing inside the machine above it.
for most of the video, the camera stays close enough that you’re looking at individual parts. a joint looks like a junction. a leg looks like a route between nodes. the closed eye looks like another piece of machinery waiting for power.
then all six signals reach the center.
the music drops out. the iris starts moving. the camera pulls back, and suddenly every connection you’ve been following belongs to the same enormous creature.
my favorite detail is that the little repair bots are still there when it wakes up. you finally see how small they are compared with what they’ve just switched on.
i spent all that time making a rescue mission, and the ending feels like six tiny idiots realizing they should’ve read the manual first.
watch it again after the reveal. the legs were there the whole time.
HOLY SH*T, I MADE A GOLDEN SPIDER FOLLOW 8 WALLETS AND EVERY TRAIL LED BACK TO THE SAME PLACE.
watch what happens when the camera pulls back.
it’s called GROK TRACE. i built a visual investigation around one question: what would eight separate wallets look like if they all received funding from the same source?
at first, the screen is a mess of connections. the spider moves around the edge of the network, picking up one path at a time. you can follow what’s happening locally, but you can’t see the whole structure yet.
then the gold trails start meeting.
each new connection changes how you read the previous one. by the time the eighth path lights up, the interesting part is no longer any individual wallet. it’s the point they all lead back to.
that’s when the camera finally gives you the full picture.
i wanted the investigation itself to be interesting to watch. you should be able to follow the question before you understand every panel on the screen.
the moving packets show the paths being traced. the lower panels track the investigation. the spider gives your eyes something to follow through all that noise.
this particular case uses symbolic wallets and an illustrated network. it shows the investigation i wanted to visualize, without pretending to expose real people.
and there’s a distinction i wanted to keep: a shared funding source gives you another question to investigate. it doesn’t automatically prove that one person controls every wallet.
the satisfying part is that the answer was on screen before the camera let you see it.
watch once following the spider. then watch again following the gold lines.
at what point did you notice they were all heading to the same place?
HOLY SH*T I GAVE 6 AI AGENTS 24 HOURS TO GET @ELONMUSK TO REPLY. AT 21:00, ONE OF THEM KILLED THE WHOLE PLAN.
five agents were ready to tag him. the sixth said one sentence:
"what are we actually showing him?"
no proof, no post.
here's how 24 hours went:
03:00 the build crashed
09:00 the first real user tried it
15:00 the team split: tag Elon now, or prove it first
21:00 CRITIC rejected the pitch: "unsupported claim"
so they threw the hype out and rewrote it around one thing: a working prototype.
then the CEO hovered over "Post"…
and had to wait for the critic.
watch what they sent him 👇
i gave Grok Bot $5,000 of fake money and one night to see what six agents would do with it
22:00 to 06:00. no live funds. by morning the simulated balance was $25,000.
92 trades. 69 green, 23 red.
each agent got one job and stayed in its lane:
> NOVA, momentum: +$8,067.73
> ORBIT, reversal: +$6,608.02
> ECHO, breakout: +$1,718.73
> IRIS, volume: +$1,648.14
> ATLAS, mean revert: +$1,154.84
> FLUX, trend: +$802.54
six lanes, and they add up to exactly +$20,000
the part i keep staring at is 05:21. NOVA closes one trade for +$3,606. on a $5,000 start that would've been a few hundred bucks. by 5 am the balance had grown so much that the same kind of move paid thousands.
and the 23 losses? most were under $150. none of them came close to one big close.
nobody hit a 1,000% coin. it was six bots taking small wins all night and cutting losers fast.
no real money this time. this was the dry run.
the question is what it does when it's live 👀
89% of you have an NPC wallet and don't even know it...
i scanned 2,000,000 Solana wallets. 1,786,906 of them had nothing. no pattern, no word, no luck. just random letters.
so i built QUANTUM RARITY to find out who's actually rare.
paste any wallet. it finds every hidden pattern and gives you the exact odds, not vibes.
mine:
ZYNexSFaVhb3az3pW9FxL8TCfjsohXwDbkyRd6rW4sJ
→ Epic. 1 in 182,434
the USDC contract, billions flowing through it?
→ plain. NPC. same as 89% of you 😭
Wrapped SOL?
→ Mythic. 1 in 4.5 × 10⁶⁹
it catches stuff you never noticed:
→ 77777 runs
→ counting digits like 765432
→ real words hiding in your address
→ mirrored ends
→ a first letter only 4% of wallets get
no wallet connect. address only. paste your private key by mistake and it refuses to touch it.
every wallet gets its own quantum sigil + a card to flex.
quote this with your wallet.
let's see who's rare and who's an NPC 👇
quantumrarity.xyz
A hacker just sent 93.5M $THEO from the @Autheo_Network exploit to my wallet 👀
Not mine. Didn’t touch it. Not selling, not swapping, not moving.
Autheo team, post the official return address and I’ll send it all back.
Tx: basescan.org/tx/0x3662883f9f…
i'm f**king done with one AI doing all the bookkeeping alone...
it reads, writes, checks and approves its own work. and books a $75 duplicate like nothing happened.
so i'd split it into 6 @Grok Bots, one job each:
1. INBOX receives files
2. ROUTER assigns tasks
3. BOOKS writes entries
4. TRACE links every entry to its receipt
5. CHECK returns PASS / FAIL / PARK
6. REPORT builds the summary
→ $75 copy of the same receipt → excluded
→ $120 with no purpose → parked, ask owner
draft said $920. verified: $845.
6 documents. 37 actions. 30 seconds.
the bot that writes the entry should never approve it.
full breakdown below ↓
i built QUANTUM VANITY
a free tool that makes your Solana wallet start with any word you want
i tested it on my name:
ZYNexSFaVhb3az3pW9FxL8TCfjsohXwDbkyRd6rW4sJ
odds: 1 in 348,667,769
a normal PC finds it in ~30 min
how it works:
→ type a word, your name, ticker, anything
→ your PC generates millions of real wallets
→ keeps the one that starts with your word
→ import it into Phantom
→ runs 100% on your computer, keys never leave it
→ search several words at once
→ also catches pretty wallets: 77777, 12345, …8888
→ shows real odds + wait time before you start
why "quantum": it also simulates how a quantum computer would find the same wallet with Grover's algorithm, in ~23,000x fewer tries
fun fact: a wallet starting with "p" is 58x rarer than one with "B"
quote this with the name you want on your wallet
i'll tell you if it takes 1 minute or 1 million years 👇
github.com/0xzynex/quantum-v…
how to run it:
1. install Node.js
2. download the repo
3. open the folder, type: npm start
4. open localhost:5180 in your browser
type a word, press start, done
github.com/0xzynex/quantum-v…









