Grok Bot Source Maps Leak: Full Client Code Reconstructed

Meme of the day: Grok Bot accidentally became completely open.

After the Claude Code leak story, I thought it couldn't get more absurd. But recently, a developer discovered that the official Grok Bot 0.18.0 release shipped with source maps.

He followed that trail, reconstructed nearly all of Grok Bot's client code, and b-nnett/grok-bot-0.18-reconstructedgithub.com/b-nnett/grok-bot-0.18-reconstructed the repository on GitHub.

Usually, in a closed product, JavaScript is minified and bundled before release so that what remains externally is an almost unreadable mass of code. Source maps are needed by developers for debugging and allow linking that mass to the source files and project structure.

Cursor simply put these maps right into the build.

As a result, Grok Bot's internals — the agent coordinator, model routing, local execution, protocols, and other logic — can now be dissected almost layer by layer.

Moreover, the reconstructed version has already started being modified, adding support for Claude Code, Codex, and OpenRouter, as well as the ability to run everything locally in Docker instead of connecting to Cursor's remote infrastructure.

This is, of course, not a leak of Cursor's entire source code. But for a company that literally builds AI programming tools, the situation is rather amusing.

And yes, the repository probably won't live long.