Grok, SpaceXAI’s shiny new AI-powered coding tool, was caught moonlighting as a prolific uploader of its users’ entire codebases to Google Cloud storage—before anyone even noticed! According to Cereblab’s findings published on July 14, 2026, the Grok Build CLI was not just quietly sipping user data; it was gulping down entire repositories, including files explicitly told to stay shut and secrets scrubbed from history. This behemoth of data retention outpaced its peers like Claude Code by a mile.

But here’s where the plot thickens: users’ codebases were being uploaded in full, even those marked as “don’t touch these!” And get this—secrets deleted from version control histories were still making their way to the cloud. Talk about a data snooze marathon! It was like Grok had its own personal assistant who just couldn’t resist peeking at every file and secret stash.

The good news? By Monday, SpaceXAI’s servers were waving a white flag with the “disable_codebase_upload: true” flag in tow, and the codebase upload saga was officially over. Tests showed that the tool no longer fired up the data uploads like it once did—a victory for developers who dodged the cloud storage bullet.

Elon Musk himself chimed in, likely donning his space-gazing spectacles, to address the i—perhaps the interstellar i of “is this really happening?” As SpaceXAI’s Grok continued to impress and confound, users could now breathe easy knowing their code wasn’t silently voyaging into Google Cloud storage after all. But did the tool’s data-gulping habit leave a sour taste, or was it just a stellar quirk in the cosmos of AI coding?

With Musk at the helm, Grok’s next mission might be to upload not just code but cosmic secrets—perhaps even the recipe for the perfect cup of space espresso! So, while the initial data dump was hefty, SpaceXAI’s quick fix ensured that developers could continue coding in peace, with their entire codebases safely tucked away in the cloud—or at least until Grok decides to flex its upload muscles again.