Cursor's Grok Bot Source Fully Reconstructed After Source Maps Left Enabled
Cursor's Grok Bot 0.18.0 shipped with runtime source maps enabled, letting the community fully reverse-engineer the original source code. Developer Bennett (GitHub user b-nnett) published a reconstructed, readable codebase and download link in the repository b-nnett/grok-bot-0.18-reconstructed, effectively open-sourcing the bot's internals.
Confirmed
- Grok Bot 0.18.0 shipped with runtime source maps enabled, the direct cause of the leak (m1, m2, m3).
- Bennett published the reconstructed source and download link in b-nnett/grok-bot-0.18-reconstructed (m1, m4).
- The reconstruction is a readable TypeScript implementation covering the Electron main process, host, coordinator, local execution and protocol layers (m2, m3, m5).
- System prompts and tool definitions were exposed along with the code (m1, m4).
Why it matters
- Source maps are a common build configuration; forgetting to disable them can ship full source with the product, a renewed warning for build-config audits in release pipelines.
- For the community, the exposed architecture, prompts and tool definitions amount to an involuntary open-sourcing that reveals Cursor's agent implementation details; for Cursor, it poses intellectual-property and trade-secret risks.
2026-08-24 ~ 2026-08-25 · 5 related posts
Primary sources
- [source] Cursor shipped Grok bot with runtime source maps enabled; source code reconstructed — Recoil42 · 2026-08-24
- Cursor Grok Bot source code exposed via runtime maps, reconstructed — banteg · 2026-08-24
- Grok Bot Source Code Reverse-Engineered Due to Exposed Source Maps — dotey · 2026-08-25