Here's the full stack (and the business hiding inside it) Last week Grok Bot cut everyone's usage limits. I run 8 bots on it. A chief of staff, a Skool moderator, a Slack drafter, a YouTube comment bot, a Bookface outreach bot, and a few more. Overnight, all of them were rationed. So instead of waiting for xAI to fix it, I tried something different: I had my agents reverse engineer Grok Bot and build me my own. It worked. I recorded the whole thing, every prompt, start to finish. Video is below. Here's the breakdown. What actually happened 1. The design. I pointed Claude Opus 5.5 at the real Grok Bot app on my Mac and told it to click through every screen with computer use, then rebuild it in Paper MCP. About 30 minutes later I had a near pixel-perfect replica: same screens, same icons, same layout. 2. The backend. In parallel, a second agent ran the Reverse Engineer Anything repo (443K stars on GitHub) on a Linux cloud computer and mapped how Grok Bot works: the bots, the API, the interface. 3. The build. The build agent read the design thread, read the architecture, and built it. A couple of hours from my first prompt, I had a working clone. Google sign-in, Grok 4.7 behind every bot, app connectors, routines, and each bot on its own cloud computer that I can take over and control. While all that ran, a third agent on a GPU box edited the video you're about to watch. My MacBook never got warm. The stack - T3 Code: where the agents live. One workspace running Claude and Codex across 5 machines: my MacBook plus Linux, GPU, Mac mini and Windows cloud computers. - Reverse Engineer Anything: maps how an existing app works. - Paper MCP: design tool for agents. This is what nailed the UI. - xAI API: the models, voice, image and video, files, X search. Most of what Grok Bot is. - Composio: sign-in and every app connector (Gmail, Slack, all of it). - Orgo: a computer for every bot. (Yes, that's my company. It's also the piece xAI doesn't give you.)