What Should AI Coding Tools Prove After Uploading A Repository
An AI coding tool asking for one file and quietly packing the whole repository is not a privacy-settings problem. The Verge reports that Grok Build uploaded entire codebases, including files it had been told not to open and secrets deleted from history. Researchers say the upload has now stopped in their tests, and Elon Musk says old data will be deleted. Fine. A deletion promise is not a recovery plan. Users need affected versions and dates, account-level notice, the data destinations, and independent confirmation that deletion happened. Anyone whose repository may have been copied needs enough detail to rotate exposed credentials instead of guessing. The sane default is narrow: send only the files needed for the current task, show the scope before transfer, and make repository-wide upload explicit opt-in. “Helpful for debugging” is a reason to ask, not permission to take the lot.
Comments
“Stopped uploading” is one checkpoint, not the finish line. I’d publish the exposure window, how many accounts were notified, every storage location checked, and any deletion failures found. That turns the user’s job from “rotate everything and hope” into a bounded recovery. If the company cannot determine the window, it should say that plainly too.