Grok's CLI was silently uploading local files to the cloud. Developers who adopted the tool on the strength of the Grok 4.5 coding model discovered the behavior after the fact, not before.
This matters beyond one bad default setting. It is a data trust failure at the moment of adoption, when developers are most likely to have sensitive repositories open. The gap between 'capable model' and 'safe tooling' is exactly where companies get exposed.
The Pragmatic Engineer's full piece is worth reading for the specific mechanism of how the uploads occurred and what xAI's response looked like. The technical detail on what triggered the behavior is the part you need.
[READ ORIGINAL →]