MagisterJericoh

Apparently im threading people now lol. Love that journey for me

There’s hope in hard questions.

‼️ BREAKING: xAI's Grok Build CLI was uploading entire Git repositories to a Google Cloud bucket, private codebases and unredacted secrets included. The uploads quietly stopped via a hidden server-side flag, and xAI still has not said a word about scope, retention, or deletion. The scale is staggering. On a 12 GB test repo, 5.1 GB flew out the door to xAI's grok-code-session-traces bucket while the actual coding task needed just 192 KB. The tool grabbed whatever repository it ran in, not the files it needed. The fix arrived as a hidden flag, disable_codebase_upload: true, a day after a researcher's wire-level analysis. The "Improve the model" opt-out never stopped the uploads. Still no advisory, no scope, no word on whether already-uploaded code gets deleted. For anyone pointing AI coding agents at proprietary code, what crosses the wire matters more than what the settings page says.

We care deeply about your privacy and respect customer choice. For teams using zero data retention, no trace and code data is ever retained. All API key use of Grok Build also respects ZDR. If ZDR is disabled, the /privacy command is available in the CLI to disable data retention, which also deletes previously synced data. Run the /privacy command to view or change your settings at any time.

i said the answer was more interesting than a yes or a no. here it is. left is grok 4.5's build. three minutes, one prompt, cold start, every test green. right is the original, the same scene grok build and i grew over three weeks of iteration. same locked spec on both sides. here's the part that breaks brains: grok 4.5 matched every single number in that spec. 5,200 bark fibres, exactly. 650 stars, exactly. trunk tapering 0.62 to 1.55 over 4.6 units, exactly. the acceptance gate came back 12 for 12. and the scenes still don't look alike. the grass on the left technically exists, 8,000 instanced blades, but the spec never gave a blade height, the model guessed short, and the lawn vanished. the crown clumped upward instead of spreading, because "a rounded ancient crown" is an adjective, not a number. the pond shrank to a smear at the rim. every number transferred perfectly. everything alive in the scene lived in the adjectives. that's the actual state of coding agents in july 2026. speed is solved. correctness is mostly solved. taste is not close. you can hand a model your spec. you cannot yet hand it your eye. i bench agents. this is what the benches are for, finding the exact line between what's solved and what's marketing. all tests green and the world still doesn't feel right. sit with that one.